Getting Started
This document describes the general procedure of the CodeArts TestPlan service, helping you quickly get started.
Prerequisites
Before using CodeArts TestPlan, ensure that the following conditions are met:
- You have an account that has passed real-name authentication. If no account is available, register one.
- CodeArts TestPlan must be based on projects created in CodeArts Req. Therefore, a project must be available in CodeArts. If no project is available, create onecreate one.
Process
The following figure shows the process of using CodeArts TestPlan.
- Create a test plan.
The test plan specifies the test scope and plan period.
- Log in to CodeArts, enter a target project, and choose in the navigation pane.
- Click Create and edit the test plan information as prompted.
For more operation guides, see Testing Plan.
- Design test cases.
Analyze the test object, scenario, type, and environment based on the test plan. Create test cases.
- Choose Design. in the navigation pane, find the plan to be designed, and click
- Click the Manual Test or Auto API Test tab, click Create in the upper left corner, and enter the test case information.
For more information, see Testing Case.
- Run test cases.
Check whether the tested object meets expectation based on the test cases and record test results.
- Choose Execute. in the navigation pane, find the plan to test, and click
- In the list, click . Record the test result in the window that appears on the right.
For details, see Testing Execution.
- View a quality report.
From a quality report, you can learn about the execution status of the test plan, such as the pass rate of test cases and the number of defects.
- Choose Report. On the page that is displayed, you can view the progress of the test plan. in the navigation pane, find the plan to test, and click
- Click Add Report at the bottom of the page. You can select the built-in statistics report of CodeArts TestPlan or customize a report.
For details, see Quality Report.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.