DoxRunner
Macquarie University Student Accommodation
Overview
Test Cases are normally embedded in the Solution document and are semi-structured with bookmarks and tables. This makes it unsafe to manage some operations manually.
This page describes those operations that apply to one or more Test Case and are accessed via the Solution document. All other operations such as documenting a test case or formatting the documents must be done manually.
Create a new test case
A test case is created using an external document called the Test Case Template, which must be located in the same folder as the Solution document. Because any new test case requires specific bookmarks and links in the Solution document, it is strongly advised that DoxRunner's Create Test Case operation be used to create a test case.
​
Copy a test case
Sometimes copying an existing test case is better then creating a new one from scratch. Copying a test case requires specific bookmarks and links in the Solution document, so it is strongly advised to use DoxRunner's Copy operation when copying a Test Case.
​
Rename a test case
Renaming a test case can be divided into two components:
-
Test Case ID
-
Test Case Name
Renaming the Test Case ID involves bookmarks with the Test Case ID embedded in them, so it is strongly recommended that DoxRunner's Rename operation be used.
Renaming the Test Case Name can also be done via DoxRunner's Rename operation, but if it is the only component to be renamed, it can be done manually with minimal risk.
​
Update a test case
Test Cases are designed to be updated to make them useful for performance testers, so long as their structure is preserved. That is, updating text is encouraged.
However, copying, renaming, and adding or deleting managed sections should be done using the relevant DoxRunner operation. An overview of each is set out below.
​
Manage test case sections
Each test case is created from the Test Case Template document. This document should be tailored to suit the solution. If that tailoring resulted in a section being deleted, and that section is required for a specific test case, then it is strongly advised that the section be added via DoxRunner's Manage Sections operation.
Deleting a section in a test case can be done via DoxRunner's Manage Sections operation too, but it can be deleted manually with minimal risk, so long as its associated bookmark is also deleted.
​
Check out
A test case can be deleted manually so long as its associated bookmarks are manually deleted also. Otherwise use the Performance Test Support application to delete a test case.
​
Check in
If a test case has been checked out and sent to a team member, and that team member has updated it, the Check-in operation will re-incorporate it back into the Solution document.
​
Export a test case
A test case can be deleted manually so long as its associated bookmarks are manually deleted also. Otherwise use the Performance Test Support application to delete a test case.
​
Delete a test case
A test case can be deleted manually so long as its associated bookmarks are manually deleted also. Otherwise use the DoxRunner operation to delete a test case.
​