Software upgrades often include test case template changes that add new features, change parameter options, or change the way a test operates. Changes in the system's defined SUTs, test server configuration, or a test case or test case template can require that you either repair a test case or remove it from a test session. When you open a test session, the test system checks for these conditions and notifies you of any changes that require your attention with pop-up messages and by color-coding the test cases displayed in the Session Builder tab.
When a test case is displayed in Red, the settings must be modified before the test case can be used. Red indicates one of the following conditions:
The test case template has been upgraded and one or more settings are no longer valid.
The test server configuration has changed and IP addresses used in the test case are not valid.
The test server or SUT associated with the test case has been deleted from the test system. The Change Test Server window opens automatically when you edit the test case if the test server is missing.
You must Edit... the test case and modify the settings. If the test case fails validation testing, an error message is displayed that indicates which parameter should be modified.
A test case is displayed in Green if its test case template has been modified but the parameter settings are valid. A green test case can be executed.
A test case is displayed in Gray if the test case template or linked test case has been deleted. Remove... this test case or link from the test session, as it is no longer usable.
If a test case is red or green due to a software upgrade, a list of changes that have been made to the test case is displayed when you edit the test case. The Test Case Warnings/Errors dialog lists the parameters that have been changed and indicates how the settings have been modified to accommodate the changes.
If the test case continues to show up red or green even after re-saving and re-opening the test session, this should be reported as a bug. It could mean our validation logic is not in sync everywhere, causing the test case to be “stuck green” or “stuck red”. In most cases the test case will still run properly, but depending upon the color and the nature of the bug, it may require the user to always open the test case editor and click OK to get the test to run properly. Green ones (warnings of upgrades and benign changes) should still run without needing to edit them, but red ones by their nature (errors that prevent execution) will require the user to edit the test case with the full editor (not the cross-reference).
The messages in this window include the parameter location, how it changed, and how your settings were affected. The general format of these messages is <location/protocol> - <parameter> <comment>.
Location/protocol will generally correspond to a parameter tab or a group of parameters. The location of parameters on the General tab are labeled with the test case name.
Parameter identifies the parameter by name.
Comment indicates the action taken or the error encountered. When the comment includes the word "invalid," the parameter has been changed in such a way that the current value is not acceptable. All invalid settings must be corrected before the test case can be used.
When the comment includes the word "upgraded," a change has been made to the parameter but it may not affect your test. If the parameter is new, you will normally see "set to default value." If the valid options for a parameter have changed but your setting is still valid, you will see "set to" followed by the setting.
|
TIPS:
|
Related Topics