DoxRunner
​
Overview
​
DoxRunner recognizes five rule types that do not resolve directly into a parameter:
​
​
SAP GUI
​
A SAP GUI rule defines an argument within one of the many SAP GUI functions encountered in a raw script.
​
The value of the argument is collected by a Script operation and presented to the user as an Unassociated Value in the Parameter Association form. The scripter can then associate this value with one of the seven parameter types presented in other panes of the Parameter Association form.
​
​
Headers
​
Header rules are not normally required because LoadRunner manages them reasonably well and offers facilities to manage them.
​
However there are some situations where LoadRunner doesn't recognize
a header when it should. To rectify this requires a lot of manual effort
to identify those that are missing, find where they are required, and
configure the script accordingly.
​
Once you identify them, DoxRunner provides the means to document
them and apply them to a raw script if the script needs to be re-recorded using a Script operation.
​
Non-Function Requirements (NFRs)
Non-Functional Requirements are fundamental to performance testing.
However DocRunner only provides the facility to document them.
​
Transaction Timers
Transaction Timers are fundamental to measuring response times during a performance test.
DoxRunner supports Transaction Timers by:
-
providing a framework for documenting them as rules (in a Test Case only);
-
providing a process whereby those rules can be automatically applied to a raw script using DoxRunner's Script operations.
​
