Continuous testing commands

You can use hotkey commands on your keyboard to control your options for continuous testing. To view the full list of commands, press 'h' on your keyboard. The following options are available:

Command	Description
r	Re-run all tests.
f	Re-run all tests that failed.
b	Toggle 'broken only' mode. Only the tests that were failing previously are run, even if other tests are affected by your code changes. This option might be useful if you change code that is used by many tests, but you want to only review the failed tests.
v	Print output detailing test failures from the last test run to the console. This option might be useful if there was a considerable amount of console output since the last test run.
p	Pause running tests temporarily. This might be useful if you are making many code changes, but do not want to get test feedback until you finish making the changes.
q	Exit continuous testing.
o	Print test output to the console. This is disabled by default. When test output is disabled, the output is filtered and saved, but not displayed on the console. You can view the test output on the Dev UI.
i	Toggle instrumentation-based reload. Using this option does not directly affect testing, but does allow live reload to occur. This might be useful to avoid a restart if a change does not affect the structure of a class.
l	Toggle live reload. Using this option does not directly affect testing, however, you can turn live reloading on and off.
s	Force restart. Using this option, you can force a scan of changed files and a live reload that includes the changes. Note that even if there are no code changes and live reload is disabled, the application still restarts.

Command

Description

Re-run all tests.

Re-run all tests that failed.

Toggle 'broken only' mode. Only the tests that were failing previously are run, even if other tests are affected by your code changes. This option might be useful if you change code that is used by many tests, but you want to only review the failed tests.

Print output detailing test failures from the last test run to the console. This option might be useful if there was a considerable amount of console output since the last test run.

Pause running tests temporarily. This might be useful if you are making many code changes, but do not want to get test feedback until you finish making the changes.

Exit continuous testing.

Print test output to the console. This is disabled by default. When test output is disabled, the output is filtered and saved, but not displayed on the console. You can view the test output on the Dev UI.

Toggle instrumentation-based reload. Using this option does not directly affect testing, but does allow live reload to occur. This might be useful to avoid a restart if a change does not affect the structure of a class.

Toggle live reload. Using this option does not directly affect testing, however, you can turn live reloading on and off.

Force restart. Using this option, you can force a scan of changed files and a live reload that includes the changes. Note that even if there are no code changes and live reload is disabled, the application still restarts.