Importing a Custom Automation Test Case

Background

CodeArts TestPlan allows you to generate test cases by importing files in any of the following formats:

• Excel: Excel file based on the given template

Importing an Excel File

A maximum of 5000 test cases can be imported at a time using an Excel file.

1. Log in to the service homepage, search for your target project, and click the project name to access the project.
2. In the navigation pane, choose Testing > Testing Case.
3. Click the custom execution mode tab, click Import on the right, choose Import from File from the drop-down list, and click Download Template.
4. Open the Excel template on the local PC and edit the test case information based on the comments in the template headers. The columns marked with asterisks (*) are required.

   The fields in the template are as follows.

   Field	Description
   Name	Name of a test case (mandatory). Describe the test scenario or function of a test case. The value contains 3 to 128 characters.
   ID	ID of a test case. The value contains 3 to 128 characters.
   Script Path	Relative path of the script file in the repository.
   Processor	Person who needs to complete the test case.
   Status	Status of a test case. The value can be New, Designing, Testing, or Completed.
   Result	Result of a test case. The value can be Succeeded, Failed, Pending check, Not available, Blocked, or other custom results.
   Type	Type of a test case. The value can be Function Test, Performance Test, Compatibility Test, Usability Test, Reliability Test, Security Test, and Serviceability Test.
   Level	Test case level based on the importance of the scenario or function. L0: verification of underlying functions. Each module should have 10 to 20 test cases. L0 test cases account for 5% of all test cases. L1: verification of basic functions for inherited features or before iteration acceptance. L1 test cases account for 20% of all test cases. L2: verification of important features for manual tests in non-regression versions. L2 test cases account for 60% of all test cases. L3: verification of minor and non-important functions, and exception tests on basic and important functions. L3 test cases account for 10% to 15% of all test cases. L4: verification of special input, scenarios, and threshold conditions. L4 test cases account for less than 5% of all cases.
   Iteration	Iteration to test the current test case.
   Module	Module to which a test case belongs. The module list comes from the project settings.
   Requirement ID	ID of the requirement to be associated with the test case.
   Requirement Name	Name of the requirement to be associated with the test case.
   Description	Description of the test case.
   Prerequisites	Prerequisites for executing the current test case.
   Folder	Association with a feature directory.
   Test Step	Step description and expected result.
   Expected Result	Target Value of the corresponding checkpoint.

5. Save the edited Excel file and drag it from the local PC to the Import Case from File window, or click Click or drag to add a file. and select a file from the local PC. Click Next.
6. View the import result.
   • Import successful: New test cases are displayed in the list. The number of new test cases is the same as the number of rows in the Excel file.
   • Import failed: A failure message is displayed in the upper right corner.

     Download the error list from the Import Case from File window. Modify the Excel file based on the error causes, and import again.