You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing #277 I realised it's inconsistent for ginkgo to use -r and/or requiring the packages listed out as though they are import statements.
So why did you eschew the packages spec (go help packages?)
I can understand that it's not fun to implement, but I was curious for your feelings about it.
The text was updated successfully, but these errors were encountered:
This confused me too. Concretely, trying my first gexec spec:
$ go test ./cmd/...
ok github.com/go-kafka/connect/cmd/kafka-connect 1.993s
$ ginkgo ./cmd/...
Found no test suites
For usage instructions:
ginkgo help
$ ginkgo -r ./cmd/...
Found no test suites
For usage instructions:
ginkgo help
$ ginkgo -r ./cmd
Running Suite: kafka-connect CLI Suite
======================================
Random Seed: 1470468089
Will run 1 of 1 specs
•
Ran 1 of 1 Specs in 2.004 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped PASS
Ginkgo ran 1 suite in 4.437792501s
Test Suite Passed
When writing #277 I realised it's inconsistent for ginkgo to use
-r
and/or requiring the packages listed out as though they areimport
statements.So why did you eschew the packages spec (
go help packages
?)I can understand that it's not fun to implement, but I was curious for your feelings about it.
The text was updated successfully, but these errors were encountered: