THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Then once in the shell just run testQuick . You should see that the tests are now running and when doing so you may get a failing test, i.e.
| Code Block | ||||
|---|---|---|---|---|
| ||||
[info] Run completed in 1 minute, 15 seconds. [info] Total number of tests run: 628 [info] Suites: completed 181, aborted 0 [info] Tests: succeeded 628, failed 0, canceled 0, ignored 6, pending 2 [info] All tests passed. [error] (remote / Test / testQuick) sbt.TestsFailedException: Tests unsuccessful [error] Total time: 3475 s (57:55), completed Jul 6, 2023, 12:12:07 PM |
Now if we run testQuick again it will only run that failing test. Its also possible to run testQuick in a loop which will only terminate until all tests pass while only retrying failing tests. This can be done by prefixing the testQuick command with a tilda i.e. ~testQuick.
| Code Block | ||||
|---|---|---|---|---|
| ||||
[error] (remote / Test / testQuick) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 57 s, completed Jul 6, 2023, 12:19:46 PM
[info] 1. Monitoring source files for pekko/testQuick...
[info] Press <enter> to interrupt or '?' for more options. |