Skip to content
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 integration tests #531

Open
codeallthethingz opened this issue Nov 5, 2017 · 1 comment
Open

Separate integration tests #531

codeallthethingz opened this issue Nov 5, 2017 · 1 comment
Assignees
Labels

Comments

@codeallthethingz
Copy link
Member

Currently there are long running tests (10s+) that should be separated out so that the fast tests can be run more frequently to reduce the dev cycle for developers.

@cogmission
Copy link
Collaborator

Hi @willwandering,

I'm curious if you tried the gradle command:

gradle -Pskipbench check

??

That is there so that the benchmarks aren't run and makes the gradle check command go faster.

Anyway, I'm concerned that certain tests may be skipped and that full coverage of any new development's impact may be overlooked? Also, in the build.gradle file I documented a way to run individual tests - which are more appropriate for quick testing and avoiding a full waiting period. So I'm not sure this is needed, though we can talk about it more?

Thanks for getting involved! :-)

David

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants