General Information › Suggestions for Testing

Suggestions for Testing

There are a number of ways programmers can use CA ADS Alive to test a dialog. Here are some possibilities:

• Test a dialog with an animation stop point at the beginning of each possible dialog path. Execution of the dialog will temporarily halt when the stop point is reached, and you can quickly determine the logic through which the dialog is passing.
• Test a dialog with stop points set at logical points to verify data fields. When data values such as status codes, control fields, or intermediate work fields change during a single execution, you can set stop points to trap and review the changing values.
• Test multiple conditions during one session, avoiding recompilation or regeneration. When data values control the dialog flow, you can set stop points at decision points and alter data values as needed using the RECORD command. In this way, you can exercise alternate dialog paths without creating new test data cases.
• Scroll through a record from beginning to end when the dialog has stopped. You can look for questionable values and change invalid ones before they affect further processing.
• Use the STOP command to set animation stop points to stop only when a field reaches a specific value. This will aid in determining invalid information stored in records or finding error codes when they occur.
• Run a test session in the Non-Interruptible Mode (without animation stop points). In the event of an abort, CA ADS Alive takes you to a browse session from which you can expand error messages, move to an edit session, or go back to an Animation Setup Session (the Animation Setup Session is described in detail in Chapter 2, CA ADS Alive Session).