New Raising/Unraising and Assertion Checking Options

References
Purpose:

To test the new debugging raise/unraise features such as Force Debug Mode and Restart Application

Test procedure:

1) Using both the Debug / Force Debug Mode and the toolbar toggle button to enable/disable debug mode, make sure that the debug layout is raised/unraised on each toggle of the Force Debug Mode. When in debug mode, step in, check that no change of interface has occurred as it should already be in debug mode.

2) Check that when not debugging, Restart is disabled, and that Restart is enabled as soon as debugging begins.

3) With a stepped in application, check that 'Restart' leaves the debug mode as is and that the application does indeed restart.

4) Add the following line as the first line of the root's creation procedure, io.put_string (Void), make sure that Preconditions are enabled as well as Supplier Preconditions. Run the application, there should be a 'string_not_void' precondition raised. Now from scratch step in to the application, you should be at the io.put_string line, now disable assertion checking by clicking Debug / Disable Assertion Checking, making sure that assertion checking whilst debugging is disabled, then Continue the application, the 'string_not_void' precondition should be ignored and the debugger should stop with a feature call on void target exception with the tag 'count'.

Initial Conditions:

A wizard compiled basic system.

Expected result:

As mentioned after each test step.

Test runs

IDDatePlatformResult
trr#3031 year 11 weeks agoAll platformsPassed