TestMode
Set global test run modes
- TestMode
Shortest form:
tm.Show or change how tests are run. With no argument it prints
Test: Options:and the flags that are set. Otherwise each argument is a flag:+flagturns it on,-flagoff, and a plain flag toggles it. Upper-case letters show the shortest accepted form.StopOnError(also@SOE): open a diagnostic shell when a test fails, so you can look at the chip’s state. Inside it the prompt isFAILED(<test>).0>; leave it withexit.AbortOnError(also@AOE): abort the failing test and continue with the next one.Quiet: print less.Progress: show simple progress while tests run.RANDom: run tests in random order.testrunrefuses this withTest: Random mode not supported yet.SIlent: count errors without printing them.Run: print a line when each test starts.Override: allow tests that this chip does not support. The help warns that this can crash the system.NoReinit: do not reinitialise between tests.
The built-in help does not mention
QuietandNoReinit, and its summary line leaves outAbortOnError. All three are accepted. Affects only the test framework’s settings.Unvalidated
drivshell> testmode +Progress -StopOnErrorBuilt-in help
Parameters: [+/-][StopOnError|Random|Progress|SIlent|Run|Override] ... - StopOnError requests a diagnostic shell be invoked when a test fails. This allows the user to inspect SOC state using the diagshell. - Abortonerror requests a test be aborted on failure, and execution continues with next test. - Random requests tests be run in pseudo random order - Progress requests a simple progress report be displayed as tests are run - Silent requests test error messages not be printed, but errors are counted - Run requests a message is printed when a test is dispatched Prefixing the flag with + turns on the option, - turns off the option, no +/- toggles the current option - Override allows tests not supported on the specified chip to be selected and run. WARNING: these is a high probablility the system will crash when running unsupported chips