Compatibility Test Cases

Test Case Module

Compatibility test (hardware identification)

Case Name

Compatibility_Hardware_Server

Objective

Verify whether the expected Huawei TaiShan server model is used.

Prerequisites

1. The environment preparations are complete for the compatibility test. For example, the target software has been installed and can be started; no non-default system applications are running in the environment; and the required testing tools are installed. For details, see the tool help document.
2. The dmidecode and lspci tools are available. Using CentOS 7.6 as an example, the tools come from the dmidecode.*.rpm and pciutils.*.rpm packages in the self-contained image. It is recommended to mount the ISO file and configure a yum repository for installation.

Procedure

1. dmidecode > /home/hardware_info.log
2. lspci -tv > /home/hardware_pcie.log
3. lscpu > /home/hardware_cpu.log
4. lsblk > /home/hardware_disk.log

Expected Result

The expected server model is consistent with the model detected on the test server.

Case Name

Compatibility_Software_Name

Objective

Verify whether the background process of the software to be tested exists in the Huawei TaiShan server test environment.

Prerequisites

1. The environment preparations are complete for the compatibility test.
2. The software to be tested has been started.

Procedure

1. ps -aux > product_name.log
2. cat /proc/version > system_version.log

Expected Result

The background process of the target software can be detected and identified in the process snapshot file.

Case Name

Compatibility_Application_Start

Objective

Verify whether the target software can be properly started as scheduled, with no errors occurring during the process.

Prerequisites

The environment preparations are complete for the compatibility test.

Procedure

1. Run the target software startup command or script in the configuration file of the Compatibility Testing tool. If the command or script is not configured, wait until the software is manually started.
2. Check whether the target software is started as scheduled in the system process list.
3. Check whether any new error is recorded in the /var/log/messages file.

Expected Result

1. The background process of the target software is detected in the system process file.
2. No error is reported during the startup of the target software.

Case Name

Compatibility_Application_Stop

Objective

Verify whether the target software can be properly stopped as scheduled, with no errors occurring during the process.

Prerequisites

The environment preparations are complete for the compatibility test.

Procedure

1. Run the target software shutdown command or script in the configuration file of the Compatibility Testing tool. If the command or script is not configured, wait until the software is manually stopped.
2. Check whether the target software is stopped as scheduled in the system process list.
3. Check whether any new error is recorded in the /var/log/messages file.

Expected Result

1. The background process of the target software is not detected in the system process file.
2. No error is reported during the shutdown of the target software.

Case Name

Compatibility_Idle_Cpu

Objective

Verify the CPU utilization fluctuation before and after the target software is started.

Prerequisites

1. The environment preparations are complete for the compatibility test, that is, the test environment must remain idle (no load).
2. The target software can be started, and the load can be increased so that CPU utilization exceeds the default idle level after startup. The load may be generated using a performance testing tool selected based on user-specific service characteristics (configurable in the configuration script of the Compatibility Testing tool) or through manual service simulation.
3. The sar tool is available. Using CentOS 7.6 as an example, the tool comes from the sysstat.*.rpm package. It is recommended to mount the ISO file and configure a yum repository for installation.

Procedure

1. Before starting the target software, record the Average %idle value (X) of the CPUs by running the following command:

   # sar -u 2 5

2. Start the target software, keep services running under a certain pressure for 5 minutes, and then stop the software.
3. After the target software is stopped, record the Average %idle value (Y) of the CPUs by running the following command:

   # sar -u 2 5

4. Calculate the CPU utilization fluctuation before and after the test (Y−X).

Expected Result

The CPU utilization fluctuation is smaller than 1%.

Case Name

Compatibility_Idle_Memory

Objective

Verify the memory utilization fluctuation before and after the target software is started.

Prerequisites

1. The environment preparations are complete for the compatibility test, that is, the test environment must remain idle (no load).
2. The target software can be started, and the load can be increased so that CPU utilization exceeds the default idle level after startup. The load may be generated using a performance testing tool selected based on user-specific service characteristics (configurable in the configuration script of the Compatibility Testing tool) or through manual service simulation.
3. The sar tool is available. Using CentOS 7.6 as an example, the tool comes from the sysstat.*.rpm package. It is recommended to mount the ISO file and configure a yum repository for installation.

Procedure

1. Before starting the target software, record the Average %memused value (X) of the memory by running the following command:

   #echo 3 > /proc/sys/vm/drop_caches
   #sar -r 2 5

1. Start the target software, keep services running under a certain pressure for 5 minutes, and then stop the software.
2. After the target software is stopped, record the Average %memused value (Y) of the memory by running the following command:

   #echo 3 > /proc/sys/vm/drop_caches
   #sar -r 2 5

3. Calculate the memory utilization fluctuation before and after the test (Y−X).

Expected Result

The memory utilization fluctuation is smaller than 1%.

Case Name

Compatibility_Idle_Disk

Objective

Verify the disk utilization fluctuation before and after the target software is started.

Prerequisites

1. The environment preparations are complete for the compatibility test, that is, the test environment must remain idle (no load).
2. The target software can be started, and the load can be increased so that CPU utilization exceeds the default idle level after startup. The load may be generated using a performance testing tool selected based on user-specific service characteristics (configurable in the configuration script of the Compatibility Testing tool) or through manual service simulation.
3. The sar tool is available. Using CentOS 7.6 as an example, the tool comes from the sysstat.*.rpm package. It is recommended to mount the ISO file and configure a yum repository for installation.

Procedure

1. Before starting the target software, record the Average %util value (X) of the disks by running the following command:

   #sar -d -p 2 5

2. Start the target software, keep services running under a certain pressure for 5 minutes, and then stop the software.
3. After the target software is stopped, record the Average %util value (Y) of the disks by running the following command:

   #sar -d -p 2 5

4. Calculate the disk utilization fluctuation before and after the test (Y−X).

Note: Filter out disk data not related to the execution of the target software.

Expected Result

The disk utilization fluctuation is smaller than 1%.

Case Name

Compatibility_Idle_Network

Objective

Verify the network utilization fluctuation before and after the target software is started.

Prerequisites

1. The environment preparations are complete for the compatibility test, that is, the test environment must remain idle (no load).
2. The target software can be started, and the load can be increased so that CPU utilization exceeds the default idle level after startup. The load may be generated using a performance testing tool selected based on user-specific service characteristics (configurable in the configuration script of the Compatibility Testing tool) or through manual service simulation.
3. The sar tool is available. Using CentOS 7.6 as an example, the tool comes from the sysstat.*.rpm package. It is recommended to mount the ISO file and configure a yum repository for installation.

Procedure

1. Before starting the target software, record the Average rxkB/s value (X1) and txkB/s value (X2) of the network by running the following command:

   #sar -n DEV 2 5

2. Start the target software, keep services running under a certain pressure for 5 minutes, and then stop the software.
3. After the target software is stopped, record the Average rxkB/s value (Y1) and txkB/s value (Y2) of the network by running the following command:

   #sar -n DEV 2 5

4. Calculate the network utilization RX fluctuation and TX fluctuation before and after the test, that is, (Y1–X1)/X1 and (Y2–X2)/X2 respectively.

Note: Filter out NIC data not related to the execution of the target software.

Expected Result

Both the network utilization RX fluctuation and TX fluctuation are smaller than 1%.