Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
CodeArts TestPlan
CodeArts TestPlan
- Service Overview
- Getting Started
-
User Guide
- Service Entries
- Testing Plan
- Testing Design
- Testing Management
-
Testing Case
- Introduction
- Test Case Library
- Manual Test Cases
-
API Automation Test Cases
- Creating an API Automation Test Case
- Writing an API Automation Script
- Keyword Library
- API Keywords
- Combined Keywords
- Importing cURL to Generate Test Scripts
- Setting an API Request
- Setting a Test Checkpoint
- Setting Response Extraction
- Importing a Postman File
- Inserting Logic Control
- Setting Test Case Parameters
- Setting Environment Parameters
- Importing an API Automation Case
- Executing an API Automation Test Case
- Custom Automation Test Cases
-
Advanced Configurations of API Automation
-
Built-in Functions
- Binary Addition Operation
- Binary Subtraction Operation
- Binary Multiplication Operation
- Binary Division Operation
- Obtaining the Current Timestamp
- Obtaining a Specified Timestamp
- Converting a Date into a Timestamp
- Converting a Timestamp into a Date
- Timestamp Addition and Subtraction Operations
- Generating Base64 Encoding
- Generating SHA512 Encoding
- Generating an MD5 Hash Value
- Generating a Random Number in a Specified Range
- Generating a Random String of a Specified Length
- Generating a UUID
- Obtaining an Array via Reverse Index
- Obtaining the Element Values of an Array via Reverse Index
- Converting Uppercase Letters into Lowercase Letters
- Converting Lowercase Letters into Uppercase Letters
- Concatenating Strings
- Cutting Strings
- Advanced Extraction Types
-
Built-in Functions
- Adding Test Cases in Batches
- Managing Test Cases in the Features Directory
- Test Cases and Requirements
- Test Cases and Defects
- Commenting on Test Cases
- Filtering Test Cases
- Customizing Columns to Be Displayed in the Test Case List
- Testing Execution
- Quality Report and Assessment
- Settings
- Roles and Operation Permissions
-
FAQs
- What Do I Do If No Test Case Exists in a Test Suite?
- What Can I Do If I Do Not Have the Operation Permission?
- Why Am I See a Message Indicating that an API Automation Test Suite Is Being Executed or Queuing?
- What Do I Do If a Test Suite ID Does Not Exist?
- Why Can't I Download the Document in a Manual Test Case?
- What Do I Do If No Test Case Exists In a Test Plan
- Why Can't I Add Work Items of the Task Type When a Test Plan Is Created or Updated?
- What Do I Do If Test Cases Cannot Be Associated with Work Items of the Task Type?
- What Do I Do If the Test Case Completion Rate in the Test Report Is Lower Than 100%?
- Why Is the Status of Test Cases in a Test Plan Inconsistent with That in a Test Case Library?
- How Are Variables Passed Between Steps in API Automation Cases?
- How Do I Set Checkpoints for Test Procedures in API Automation Cases?
- Best Practices
On this page
Show all
Help Center/
CodeArts TestPlan/
FAQs/
What Do I Do If the Test Case Completion Rate in the Test Report Is Lower Than 100%?
What Do I Do If the Test Case Completion Rate in the Test Report Is Lower Than 100%?
Updated on 2023-11-28 GMT+08:00
Symptom
A test plan is created and a report is generated after all test cases are executed. However, on the quality report page, the test case completion rate is lower than 100%.
Root Cause
The completion rate of test cases is 100% only when the result of all test cases in the test plan is Completed.
Solution
- Click Testing Case in the navigation pane. The Testing Case page is displayed.
- Click
next to Test case library and select the test plan to be viewed.
- On the Manual Test tab page, select all cases in the case list and click Batch Update Property.
In the dialog box that is displayed, select Status and set the status to Completed.
- Return to the quality report page to view the case completion rate.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.