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
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: