DoxRunner
​
Documentation
Overview
DoxRunner only recognizes three documents:
-
Solution document;
-
Test Case document (embedded in the Solution document or as a separate document when checked-out).
​
All are semi-structured because they must balance the need to document performance tests flexibly and to take advantage of the ability of DoxRunner to use the documentation to enhance LoadRunner scripts.
Microsoft Word is used for all documentation. LoadRunner contains many text files, and these are viewed as Word documents when they are being manipulated by DoxRunner operations.
​
Solution document
This is the document you will spend most of your time in.
​
It contains test cases and all elements for performance testing a solution.
​
A solution can be defined simply as a group of test cases. The group may represent a solution, or simply a group of test cases that are logically related.
An organisation may have one or more solutions depending on the applications being tested.
Each solution should reside in its own folder for ease of administration.
​
Test Case document
Test cases are normally contained within a Solution document.
If the solution is being tested by a distributed team, each test case can be checked out into its own document, sent to a team member, then checked back in if it was updated. In this case it is assumed that the team leader has responsibility for the entire Solution document.
​
Test Case Template
The Test Case Template, as the name suggests, is a skeleton that is used when creating a new Test Case.
​
It allows you to tailor how a new Test Case looks within the defined Test Case structure.
​
It must reside in the same folder as the Solution document.
​