What's new — Project Productivity Proj-579 Rule Test Riders

• Previously, adding new pages and other whole page actions were flagged as the test case failing. Now, actions involving whole pages are flagged as differences, and the user has the option of using the Overwrite button to overwrite the test case with the new results.

Help updated 12/8/2010

• Previously, if the clipboard was not in a known clean state, the recording of a test case for an activity would include any pages in the clipboard. Upon test case playback, unless the clipboard was in the precise same unclean state, those pages would be reported as differences. The user would have to intuitively know to clear the clipboard before recording the activity test case. With this enhancement, there is a Clear Clipboard button the user can click to clear the clipboard before recording the activity test case.

Help updated 12/8/2010

• Previously, there was no way to re-record a test case using the same name (basically updating the test case with new behavior of the tested rule). The user was forced to delete the existing test case rule, and then recording. With this enhancement, users can select a Re-record action on a test case listed on the landing page, and after running through the rule, save under the existing test case name.

Help updated 12/8/2010

• Previously, property differences for properties on embedded pages were not ignored at the class level of the embedded page. With this enhancement, users can ignore properties on embedded pages using the model at the class level of the embedded page.

• This enhancement is support of a style of testing called white list testing. Users specify which properties they are especially interested in monitoring whether those properties have changed in development. This style of testing can be thought of as the opposite of using ignored properties. Previously, users can specify what properties they do not care about monitoring in testing. With white list testing, users specify what properties they care about, and by inference, that they want to ignore all others.
• A new button (Manage White List) is added to the Results tab of the test case rule form for activity test cases to support this enhancement. A new property selector is delivered that opens when the Manage While List button is clicked, for the user to select the white-listed properties for the test case.

• Work to ensure that activity test cases that are white list test cases can be played back using all of the ways we currently play back test cases (manually within PRPC, as part of test suites, from TMF, etc)

• This story is about getting the re-record story (see above) working for flow test cases and resume test cases.

Note: When the Flow rule form becomes harness-based, the re-record option will also be available on test cases in the Test Cases tab. Then the Flow - Test Cases help will need to be updated to mention that option.

• Template options, RuleSets, work types, application, and work type criteria are refreshed down the left nav based on the previous selection
• Application and work type checkbox criteria are not cleared out based on changes to RuleSets and work types
• Step for Capture includes screen capture, models used for screen capture, as well as Entity-Relationship Diagram (ERD) info.

• Change Doc Wizard template
• New Corr or Word sections

• Options to include/exclude chapter content (GRP-24300) with proper validation (GRP-24299)

• A new standard system table is added in this release to support automated unit testing functions.