📄️ Session Testing
irVerify allows users to persist and reload data to facilitate the testing process. Saving and reloading data enables a user to rely upon an already-created test case for verification of rule applications as part of the rule development life cycle.
📄️ Testing Overview
Session tabs in irVerify are the areas for entering test data, viewing rule execution paths, applying
📄️ Comparing Single Tests
Each time a user presses the Test button in irAuthor, a new session tab is created in irVerify. Each
📄️ Ribbon: Saving and Loading Test Data
Saving test data
📄️ Detail Pane: Summary
Upon applying rules, the Summary tab will display the rule execution statistics.
📄️ Detail Pane: Notifications
If the rule application contains any rules that fire notifications, the output messages will be returned in irVerify in the Notifications tab. Notifications represent a great way to determine if rules have fired, thereby enriching the testing experience.
📄️ Detail Pane: Errors
Whenever a rule application is tested, the rule engine checks all the elements and rules within the entity to ensure validity of the expressions and consistency among rules. If there are any errors, the testing tool displays the errors in the error pane.
📄️ Detail Pane: Entities
The Entities tab displays all entities that are part of the current test. If an entity contains collection members or entity-based fields, those items will also be displayed in the Entities pane.
📄️ Detail Pane: Watch List
A Watch List allows users to view the values of specific elements from across the entity structure in a single, manageable view. When rules are applied, values for the elements are displayed in the Watch List.
📄️ Detail Pane: State Changes
The state changes tab will highlight any changes to values in the entity schema.
📄️ Detail Pane: Validation Changes
The Validation Changes tab will display any constraint value changes during rule execution.
📄️ Detail Pane: Rule Engine Feedback
The Rule Engine Feedback pane is a list of actions and information related to rules that are fired as the result of changing input data or applying a rule set.
📄️ Testing Rule Flows
Rule flows are considered to be explicit rule sets. In irVerify, both explicit rule sets and rule flows must be manually triggered by pressing the apply button next to it's definition in the tester window.
📄️ Ribbon: Rule Tracing
The InRule Rule Engine provide rule tracing as a way to obtain a detailed log of events that occur during execution to aid the debugging of a rule application. Rule traces are accessible in irVerify as well as from irSDK.
📄️ irVerify Options
Configuring irVerify Options
📄️ Configuring Endpoint Overrides
Select file -> EndPointOverrides
📄️ Ribbon: Viewing Test Data and Reports
Viewing test data
📄️ Evaluation Debug Display
Pressing the element drop down button next to any calculation element opens the evaluation detail