-
Notifications
You must be signed in to change notification settings - Fork 15
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
separate redis test from the unit test #99
Comments
The separation is already done via the |
Yeah but that tag says to run the redis tests. I am saying dont do that as part of test-unit. Instead do that as test-integration |
Sorry, that tag is poorly named. It enables the redis tests, which run in addition to all the other tests. Thoughts on these test targets? test-all:
// runs all tests, including integration
$(DOCKER_CMD) go build -tags="testredis" $(glide nv)
test-unit:
// runs only unit tests, with no external dependencies
$(DOCKER_CMD) go build $(glide nv) |
yeah. i would love to be able to just run the integration tests though. |
Is what im thinking we should do |
@jchauncey we could add capability to run just integration tests by checking a |
This issue was moved to teamhephy/logger#6 |
Since we are having to start an external component we are mixing terms when we call the test suit unit tests. Therefore, we should move the redis tests out to an integration target.
The text was updated successfully, but these errors were encountered: