Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
testcase_report [2020/04/26 03:33] 127.0.0.1 external edit |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Test Case Report / Manual Test Case Execution ===== | ||
- | //>> | ||
- | |||
- | // | ||
- | |||
- | Test Case Report consists of //Summary, Requirements, | ||
- | |||
- | With //ALM// integration (requires ALM plugin), you can also raise the defects to your ALM system directly. | ||
- | |||
- | Note what's described in this document are only available when [[seqoutplugin|SeqOut]] plugin is used. For models using other plugins like [[selenium_plugin| Selenium]] plugin, you can still output test cases into text file or html file in your own format when you turn on //Output Comment// in [[ModelNode | Model Property]] dialog to have all MScript comment tags to be written out to the test case report file. | ||
- | |||
- | ---- | ||
- | |||
- | ==== Access Test Case Report ==== | ||
- | Test Case Report can be accessed from // | ||
- | |||
- | {{http:// | ||
- | |||
- | ---- | ||
- | ==== Test Case Report UI ==== | ||
- | When //Test Case Report// is first open, it displays the //Summary// page. To access other pages of //Test Case Report//, hover your mouse over //Menu// at the upper-left corner of the screen to bring up the navigation pane. | ||
- | |||
- | {{http:// | ||
- | |||
- | |||
- | Click on the tabs for different section of the test case report. | ||
- | |||
- | //KPI// field shows the //Key Performance Indiciators// | ||
- | |||
- | The icon buttons on the right is the customizable toolbars. | ||
- | |||
- | ---- | ||
- | ==== Tab Summary ==== | ||
- | |||
- | //Summary// tab (shown above) provides a summary of the model execution that produced the test cases. | ||
- | |||
- | The model properties, execution parameters and the test coverage graph are displayed. | ||
- | |||
- | Click on //Open Graph in New Window// link to open the test coverage of the model execution. The covered transitions are colored in green while un-covered transitions are colored in red and partially-covered transitions are colored in yellow. | ||
- | |||
- | {{http:// | ||
- | |||
- | ---- | ||
- | |||
- | ==== Tab Requirements ==== | ||
- | {{http:// | ||
- | |||
- | |||
- | // | ||
- | |||
- | The requirements are listed in columns and test cases are listed in rows. | ||
- | |||
- | By default requirements are identified by a sequential number but you can show the requirement name/code by clicking on '' | ||
- | |||
- | The cells shaded (light blue colored) indicates that particular requirement is covered by the test case displayed in the row. So at a glance you can clearly see if any requirements have not been covered. | ||
- | |||
- | As the test cases are executed and status recorded in // | ||
- | |||
- | Clicking on the test case number will take you to //Test Case// page for that test case. | ||
- | |||
- | The column '' | ||
- | |||
- | The column '' | ||
- | |||
- | |||
- | ---- | ||
- | ==== Tab Preamble ==== | ||
- | Displays the test setup instructions the model generated. | ||
- | |||
- | ---- | ||
- | ==== Tab Test Cases ==== | ||
- | {{http:// | ||
- | |||
- | //Test Case// tab contains a series of individual test case pages each shows the details of a test case. | ||
- | |||
- | Click on the individual //Test Case// on the left to display the test case details on the right. | ||
- | |||
- | Each test case when executed or partially executed will show a vertical color bar to the right to indicates the status of the test case. | ||
- | |||
- | A test case is '' | ||
- | |||
- | A test case is '' | ||
- | |||
- | A test case is '' | ||
- | |||
- | The link at the top center of the page takes you to the Test Case Graph representing the test case steps in a graph or Message Sequence Chart (MSC) (depending on how you configure your model). | ||
- | |||
- | A test case consists of a series of steps and each step may contain many verification items. | ||
- | |||
- | Test steps are listed in the table with instruction displayed in the left column and the verification instruction on the right. | ||
- | |||
- | You can mark verification item within each step by clicking on the status buttons (passed, failed, and blocked). | ||
- | |||
- | The test step status and test case status are derived from the status of all verification items and is updated automatically in realtime as you update the status of verification items. | ||
- | |||
- | |||
- | ---- | ||
- | ==== Tab Postamble ==== | ||
- | Displays the test teardown instruction the model generated. | ||
- | |||
- | |||
- | ---- | ||
- | ==== Tab Exec Status ==== | ||
- | {{http:// | ||
- | |||
- | //Exec Status// tab summarizes the test case execution status as test cases are executed and status recorded in //Test Case// pages. | ||
- | |||
- | //Test Case Matrix// section contains the test case execution progress while // | ||
- | |||
- | Clicking on the test case number takes you to the specific //Test Case// page. | ||
- | |||
- | |||
- | |||
- | ---- | ||
- | ==== Progress Progress ==== | ||
- | |||
- | {{http:// | ||
- | |||
- | // | ||
- | |||
- | The charts are automatically updates as test cases are executed and status are recorded with //Test Case// pages. | ||
- | |||
- | Use the control buttons above each chart to filter the chart by test case status or to change the chart type. | ||
- | |||
- | |||
- | ---- | ||
- | ==== Tab Defects ==== | ||
- | If //ALM// is enabled, you will see a list of known defects raised so far by the current model from previous test execution. | ||
- | |||
- | {{http:// | ||
- | |||