Studio:Reporter: Difference between revisions
Jump to navigation
Jump to search
(New page: = Introduction<br> = The STRIDE Reporter allows you to track and report test cases for scripts, store test data in XML format, and produce HTML output for viewing of test case results. =...) |
No edit summary |
||
| Line 1: | Line 1: | ||
= Introduction<br> = | = Introduction<br> = | ||
The STRIDE Reporter allows you to track and report test cases for scripts, store test data in XML format, and produce HTML output for viewing of test case results. | The STRIDE Reporter allows you to track and report test cases for scripts, store test data in XML format, and produce HTML output for viewing of test case results. | ||
The STRIDE Reporter tracks two primary objects: Suites and Test Cases, which are further described as follows: | |||
The STRIDE Reporter tracks two primary objects: Suites and Test Cases, which are further described as follows: | |||
* A Suite is a collection of TestCases and other Suites. A Suite has a name, a description, and zero (0) or more children, which can be either TestCases or other sub Suites. | *A Suite is a collection of TestCases and other Suites. A Suite has a name, a description, and zero (0) or more children, which can be either TestCases or other sub Suites. | ||
* A Test Case represents a single pass/fail item and it consists of a name, a description, any test data that is added during the lifetime of the TestCase, and a status. The status can be any one of the following: | |||
**PASS | |||
**FAIL | |||
**IN PROGRESS | |||
**NOT APPLICABLE (or N/A) | |||
<br><br> | |||
= | =Automation API= | ||
== <br>reporter | == <br>reporter<br> == | ||
== <br>reporter.Suites | == <br>reporter.Suites<br> == | ||
== <br>reporter.Suites.Item | == <br>reporter.Suites.Item<br> == | ||
== <br>reporter.Suites.Item.CustomData | == <br>reporter.Suites.Item.CustomData<br> == | ||
== <br>reporter.Suites.Item. | == <br>reporter.Suites.Item.CustomData.Item<br> == | ||
== <br>reporter.Suites.Item.Annotations | == <br>reporter.Suites.Item.Annotations<br> == | ||
== <br>reporter.Suites.Item. | == <br>reporter.Suites.Item.Annotations.Item<br> == | ||
== <br>reporter.Suites.Item.Tests | == <br>reporter.Suites.Item.Tests<br> == | ||
== <br>reporter.Suites.Item.Tests.Item | == <br>reporter.Suites.Item.Tests.Item<br> == | ||
== <br>reporter.Suites.Item.Tests.Item.Comments | == <br>reporter.Suites.Item.Tests.Item.Comments<br> == | ||
== <br><br> == | == <br>reporter.Suites.Item.Tests.Item.Comments.Item<br> == | ||
== <br><br> == | |||
<br> | <br> | ||
Revision as of 22:47, 26 June 2008
Introduction
The STRIDE Reporter allows you to track and report test cases for scripts, store test data in XML format, and produce HTML output for viewing of test case results.
The STRIDE Reporter tracks two primary objects: Suites and Test Cases, which are further described as follows:
- A Suite is a collection of TestCases and other Suites. A Suite has a name, a description, and zero (0) or more children, which can be either TestCases or other sub Suites.
- A Test Case represents a single pass/fail item and it consists of a name, a description, any test data that is added during the lifetime of the TestCase, and a status. The status can be any one of the following:
- PASS
- FAIL
- IN PROGRESS
- NOT APPLICABLE (or N/A)
Automation API
reporter
reporter.Suites
reporter.Suites.Item
reporter.Suites.Item.CustomData
reporter.Suites.Item.CustomData.Item
reporter.Suites.Item.Annotations
reporter.Suites.Item.Annotations.Item
reporter.Suites.Item.Tests
reporter.Suites.Item.Tests.Item
reporter.Suites.Item.Tests.Item.Comments
reporter.Suites.Item.Tests.Item.Comments.Item