Creating Test Scenarios
ImportantThe Testing Scenarios feature is not available for use with the initial release of the Conversation Manager standard template and rules.
To create or modify a test scenario (for which separate create and modify permissions are needed), do the following:
- Click the Test Scenarios node.
- On the toolbar, click New Test Scenario.
- Add the following data:
- Name—A descriptive name for the test scenario.
- Description—A test scenario description
- Phase—The phase that you want the test case to execute on. For templates that do not contain phases, an asterisk (*) indicates that this phase is not applicable.
- Business Hierarchy—You can select, from a drop-down list, the level of the Business Hierarchy on which you want to run the test: for example, run at the “general/package level,” or run under a specific department or process.
- Simulated Date—You can simulate the date that the test scenario is running in order to test time-sensitive rules, such as a rule with a start/end date or business calendar. The default is to run with today's date.
- Simulated Time—You can simulate the time at which the test scenario runs in order to test time-sensitive rules, such as a rule with a business calendar. The default is to run with the current time. To clear the simulated time field, enter a dash ("-") in the hour field and press enter.
- TimeZone—You can set the time zone for the test. The time zone is applied to the Simulated Time field, and also to any time parameters in the test scenario. The default is GMT.
- Add one or more Given columns by clicking Add Given and selecting from the drop-down list. Each given represents data passed into the rule package for testing.
ImportantIf a fact's field displays in parentheses, this means that it is mapped back to more than one object in the rule template. You must select the relevant object for your test scenario. Consult the template developer if required.
- Add one or more Expectation columns by clicking Add Expectation and selecting from the drop-down list. An expectation represents the expected results from the rule execution.
ImportantIf a parameter displays in parentheses, this means that it is mapped back to more than one object in the rule template. You must select the relevant object for your test scenario. Consult the rule developer if required.
- Create one or more rows of test data. Each row represents, and is executed as, one test. Give each row a name which describes the test. Drop-down lists present all the available data options for selection, as in the rule editor, and the same tooltip as in the rule editor is also presented. But no checks are carried out on the ranges of any values, in order to enable users to specify illegal conditions for testing.
- Click Save.
This page was last modified on September 25, 2014, at 00:48.