-
-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ginkgo should run tests from both the "name" package and "name_test" package #31
Comments
I just tried this on my laptop with a simple example and it worked. Can you Onsi On Tuesday, February 4, 2014, Tim Jarratt notifications@github.com wrote:
|
I took a closer look and the behavior was a little surprising. It appears to work for some cases, but not others. cloudfoundry/cli@c197cd5 seems to exhibit this behavior for |
Methinks this is because the only file in the A simple fix for this might be to add import (
. "github.com/onsi/ginkgo"
. "github.com/onsi/gomega"
_ "cf"
"testing"
) to the |
I wasn't aware you could import a package as With that information, this doesn't sound like a real bug per se. It's already conventional to put your tests in a separate package from your package under test, so I would be willing to chalk this up to user error and consider this issue closed. |
Coo :) Yeah... _ is interesting.............
|
I was very surprised to discover that Ginkgo will only run the tests that are defined in the same package as the suite_test. Seems like a bug, but I would also accept that this is a feature (because it forces you to write your tests in the
name_test
package.Alternatively, if this is hard to solve, a warning would be very nice.
The text was updated successfully, but these errors were encountered: