SysAdmin category
About Test Cases
|
|
The Run Rule option enables the unit testing of a rule by itself before testing it within the context of an entire application. If your operator ID has the AutomatedTesting privilege through an access role, you can save the unit testing data you used for certain rule types as Test Cases. Then, the next time you test that rule, you can run the test case rather than entering the test data again.
Note: You must have the AutomatedTesting privilege to be able to work with Test Cases. For information about how to enable this privilege, see About Automated Unit Testing.
Test case rules can be created for the following rule types:
Test case rules contain both the test data and the results of that data. When you run a test case, the saved test data is used when running the rule and then compares the results to those saved in the test case. If the results do not match, investigate the tested rule to see what changed and determine whether there is a problem to be resolved.
The key to a Test Case includes the pxInsName of the rule it tests. If a tested rule is qualified by circumstance or time, create separate test cases for each circumstance.
When you have more than one test case that you want to run together or if you want to run a test case in the background, create a unit test suite rule and then use the fields on the Schedule gadget of the Automated Unit Testing landing page to run the suite. For more details about unit test suites, see About Unit Test Suites and consult the articles in the Testing Applications category of the PDN.
Use the Automated Unit Tests gadget of the Automated Unit Testing landing page to see the Test Cases that are available to you. Additionally, you can work with the Test Cases associated with a specific rule by using the Test Cases tab of the associated rule.
Test case rules are referenced in:
Test case rules are instances of the Rule-AutoTest-Case class. They belong to the SysAdmin category.