System Testing of software testing methods

System Testing 1. Basic concepts of System Testing

System testing is an integrated software system, which serves as an element of the entire computer-based system, it is combined with computer hardware, peripherals, some supporting software, data and personnel, and other system elements in the actual running (use) environment, perform a series of assembly and validation tests on the computer.

Purpose

The purpose of a system test is to compare it with the system requirement definition to find out the inconsistency or conflict between the software and the system definition, to verify the functionality and performance of the software system to meet the requirements specified in its statute. The test cases for system testing should be designed according to the requirement analysis specification and run in the actual use environment.

Method

There are many methods for testing software systems, including functional testing, performance testing, and random testing.

 

Ii. Type of system testing (1) concept of Function Testing

Function Testing: it is the most basic test in system testing. Regardless of the internal implementation logic of the software, it mainly describes the Product Requirement Specification and test requirement list, verify whether the product function meets the product specifications.

Error types found during Function Testing

Function Testing mainly aims to discover the following types of errors:

Is there an incorrect or missing function?

Does function implementation meet the hidden needs of product users and system design?

Can I accept the input correctly? Can the output result be correct?

 

Functional testing requires the test designer to be familiar with product specifications, Requirement documents, and product business functions. At the same time, the test case design methods should also be mastered, in order to design a good test plan and test cases, and conduct functional tests efficiently.

Steps for analyzing Requirement Specification

When performing a function test, you must first analyze the Requirement Specification Description, because this is the basic input for the function test. The Requirement Specification analysis can be divided into several steps:

1. label each specific functional requirement: (for those already marked in the Requirement Specification document, they can be directly referenced ).

2. Mark each hidden function;

3. analyze possible abnormal functions and mark them;

4. classify the functional requirements obtained in the previous three steps-key functions and non-key functions. The key functions refer to the functions that are essential to users, the loss of such features will cause the user to reject the product. Key features are mainly those that contribute to product availability. Sometimes users who lack such features may be dissatisfied, but will not reject the product.

5. test and analyze each function, and analyze whether it can be tested, how to test, possible input, and possible output.

6. scripting and automation.

Key Points of Function Testing

Pay attention to the following points for functional testing:

1. Consider how users can use this function, for example, whether the network is disconnected or not to access the website, and use a keyboard for operations.

2. Consider the combined use of multiple functions.

3. When multiple users access and operate the server software at the same time, check whether the simultaneous use of the software causes function failure.

 

(2) Basic concepts of Performance Testing

Performance testing is used to test the Running Performance of software in an integrated system. Performance testing can take place in all the steps during the testing process. Even at the unit layer, the performance of a single module can be evaluated using white box testing. However, the real performance of a system can be checked only when all components of the system are integrated.

The objective of performance testing is to measure the gap between the system and the predefined target. The required performance level is compared with the actual performance, and the gaps are documented.

Performance information of interest

CPU usage

Io usage

Number of I/O commands

Channel usage

Primary storage memory usage

Second storage memory usage

Execution time percentage of each module

Percentage of time a module waits for Io completion

Percentage of time used by the module on the primary storage

Tracking path of commands over time

Control the number of times from one module to another

Number of times each group of commands waited

Number of times each command page is swapped in and out

System response time

System throughput, that is, the number of processes per time unit

The execution time of all major commands.

Recommended steps for any performance test research:

1. Documented performance testing objectives. For example, the exact performance measurement criteria must be verified;

2. Define the test driver or the input source used to drive the system;

3. Define the performance methods or tools to be used;

4. Define how performance research is conducted, for example, what is a baseline, what is a change, how can it be tested when it can be repeated, and how can we know when the study has been completed?

5. Define the reporting process, such as technology and tools.

Performance testing involves a large scope, including testing performance in various business scenarios, including response time, resource usage, and system limit capacity; load Testing, stress testing, and Capacity testing are only performance tests from different perspectives.

 

System Testing of software testing methods