Updated on 2026-11-12 GMT+08:00

Execution of Security Test Cases

Execution of Security Manual Test Case

Manual Execution:

1. The partner test engineer clicks on the "Case Execution" directory on the test case list interface, and selects the security test cases.

2. Select the execution result. By default, it is "Passed." If the execution result of the test case is "Passed," you can click on the "Copy Expected Results" button in the actual result to paste the expected result content into the actual result. All security manual test cases are self-check cases, and no screenshots are required in the actual result.

3. After completing the above steps, click on the [Save the procees to the Next Use Case] button. Follow this procedure to complete the execution of all security manual test cases.

Figure 1 Manual execution of security manual test case

Batch execution:

  1. Click the [Batch Execute] button on the test case directory.
  2. In the pop-up window, select [all self-check test cases passed ] and then click [OK]. This will execute all the self-check test cases in a batch and mark them as passed.
    Figure 2 Batch execution of security manual test case

Execution of Security Automation Test Cases

Execute the security automation test case. On the test case list interface, click the [test case Execution] directory, and select the security automation scanning test case (for software deployed for customers solutions, it is the binary scanning test case; for hosted software of partners solutions, it is the web scanning test case).

Figure 3 Execution of security automation test cases

Binary scanning test case:

On the execution page, upload the binary software package file. Then, click [Execute]. After the execution is complete, you can view the result details in the execution result history.

Figure 4 Execution of binary scanning test case
Figure 5 Execution result history
Figure 6 Viewing detailed execution results
Figure 7 Viewing detailed execution results

Website scanning test case:

  1. On the execution page, enter the target URL (only supports HTTPS secure protocol) and the domain alias. The scanning mode must be set to depth scan,the website scanning test case must set up login information.
    Figure 8 Execution of Website scanning test case
    Table 1

    Parameters

    Description

    arget URL

    The URL address after logging in, for example: https://www.domain.com/home, which is the starting URL for automatic exploration.

    Domain alias

    Help users identify their domain address, you can fill in any name that is convenient for you to identify the website domain.

    Scan mode

    • Quick scan mode: shortest scan time, relatively fewer vulnerabilities can be detected;
    • Standard scan mode: moderate scan time, relatively more vulnerabilities can be detected;
    • Deep scan mode: longest scan time, can detect the deepest vulnerabilities. The partner Lead baseline certification and FTR solution certification require the use of deep scan mode.
  2. Set up login information.
    Figure 9 Set up login information
    Table 2

    Parameters

    Description

    Website Login Settings

    Please set up your login preferences to help identify more security issues for you.

    Login configurations are divided into three types: Web page login, Cookie login, and Header login.

    Login Method 1: Web Page Login

    Login Page

    Address of the website login page.

    User Name

    User name for logging in to the website.

    Password

    Password of the user name.

    Confirm Password

    Enter the password of the user name again.

    Login Method 2: Cookie Login

    cookie value

    If your website requires not only a username and password for login but also other access mechanisms (e.g., entering a dynamic verification code), it is recommended that you set up cookie-based login for website vulnerability scanning. This will enable the CodeArts Inspector service to identify more security issues for you.

    When setting up cookie-based login, you need to enter the cookie value of the website.

    NOTE:

    After obtaining the cookie value, please keep the website logged in when creating a scan task to prevent the cookie from expiring.

    The Cookie login feature of the CodeArts Inspector service supports two formats: "semicolon-separated key-value pairs" and "JSON".

    You can trim or modify the data obtained from the browser extension as needed, as long as the JSON format remains correct and the necessary cookie and storage values are provided.

    Login method 3: Header login

    Custom Header

    Configure the HTTPS request header. You can customize the request header information, for example, login using a token, by setting key-value pairs.

  3. then click [Execute]. After the execution is complete, you can view the result details in the execution result history
    Figure 10 Intelligent entry of partner software function list

Binary Vulnerability Fixing And Appeal Guide

If a partner detects viruses, high-risk, or ultra-high-risk vulnerabilities during automated security testing and scanning, the platform also provides the "Binary Vulnerability Fixing and Appeal Guidebook" to assist partners in efficiently completing vulnerability fixes. Download link: Binary Vulnerability Fixing and Appeal Guidebook