3 trace

Smart records all executions of testcases and actions. These records is used to suggestion behavioral guidance, and helpful to research problem. We call this record "omnipresent log".

Trace Demo shows how to use this record system.

1. First, create the test.

In this demo, "collaboration" testsuite is created. This testsuite contains "tc1" testcase to check if the state of the remocon is changed to "PowerOn" state from "PowerOff" state when "power" event occurs and "tc2" testcase to check if the state of the aircon is changed to "PowerOn" state from "PowerOff" state when "power" event occurs.

Figure 3 -1

2. After the test is created, then run it.

In this "collaboration" testsuite, "tc2" testcase is failed. By the failure message, "PowerOn" state of the aircon is not active.

This case is easy to resolve the failure, but we use Smart record system to find the cause of the failure. Smart records all executions, so modeler can check the log for researching the problem.

Figure 3 -2

3. Click the trace button () in the Smart Modler Tool to show logs. After click the button, open the "Trace" window. A log is shown in a sequence diagram or a text.

In this test, as a result of seeing the diagrams, we find that the reason why state of the aircon isn't chaged is that "power" event is not send to the aircon from the remcon. To see the remcon statemachine diagram, no effect activity is associated with "power" transition. So we create the "pushPwoerButton" activity and associate it with "power" transition, and run tests agein, then tests is passed.

Figure 3 -3