What test methods can be used for system testing?

Optimize the system performance test in Master Optimizer.

The basic methods of system testing are:

1. Recovery test, the recovery test mainly checks the fault tolerance of the system. When an error occurs in the system, whether the error can be corrected and the system restarted within a specified time interval. The recovery test starts with using various methods to force the system to fail, and then verifies whether the system can recover as soon as possible.

2. Security test, security test and check the system's ability to prevent illegal intrusion. During the security test, the testers pretended to be an illegal intruder, Sun Xunji, and used various methods to try to break through the defense line.

3. Strength test, strength test to check the resistance of the program to abnormal situations. Strength testing always forces the system to operate with abnormal resource allocation.

4. Performance test.

For those real-time and embedded systems.

Even if the software part meets the functional requirements, it may not be able to meet the performance requirements, although from unit testing.

Performance testing is included in every test step, but it is only when the system is truly integrated that it can be comprehensively and reliably tested and run in a real-world environment to accomplish this task.

System Testing. It is to combine the confirmed software, computer hardware, peripherals, networks and other elements together to carry out various assembly tests and validation tests of the information system, and the system test is a test for the entire product system, with the purpose of verifying whether the system meets the definition of the requirements specification, finding out the inconsistency or contradiction with the requirements specification, so as to propose a more perfect solution. After the system test finds a problem, it is necessary to debug to find out the cause and location of the error, and then correct it.

It is a black box test based on the overall requirements specification of the system and should cover all joint components of the system. The object includes not only the software to be tested, but also the hardware, peripherals, and even some data, some supporting software and its interfaces.

System testing is a series of rigorous and effective tests on the computer system in the actual operating environment to find potential problems of the software and ensure the normal operation of the system.

The main contents include:

Functional testing. That is, to test whether the software system is functioning correctly, based on requirements documents, such as the Product Requirements Specification. Since correctness is the most important quality factor in software, functional testing is essential.

Robustness test. That is, the ability to test whether the software system can operate normally under abnormal conditions. Robustness has two meanings: fault tolerance and resilience.

Black box testing, also known as functional testing, is a test to check whether each feature works properly. In the test, the program is regarded as a black box that cannot be opened, and the test is carried out on the program interface without considering the internal structure and internal characteristics of the program, which only checks whether the program functions are used normally in accordance with the provisions of the requirements specification, and whether the program can properly receive the input data and produce the correct output information. Black-box testing focuses on the external structure of the program, regardless of the internal logical structure, and mainly focuses on the software interface and software functions.

The white-box test, also known as the structural test or logic-driven test, is based on the internal structural test program of the program, through the test to detect whether the internal action of the product is carried out normally in accordance with the provisions of the design specification, and to check whether each channel in the program can work correctly according to the predetermined requirements. In this method, the test object is regarded as an open box, and the tester designs or selects test cases according to the information about the internal logical structure of the program, tests all the logical paths of the program, and determines whether the actual state is consistent with the expected state by checking the state of the program at different points.

Boundary value analysis is a black-box test method for testing the boundary values of inputs or outputs. Usually the boundary value analysis method is used as a supplement to the equivalence class partitioning method, in which case the test cases are derived from the boundary of the equivalence class.

The above are some theories, and I will give you an example

For example, the test object is the three sides of a triangle.

Then the boundary values of the three edges are from greater than 0 to positive infinity, and the sum of the two edges is greater than the third edge.

When you design your test data, you need to design it based on its boundary values. For example, if -1 0 1 is tested using the boundary value analysis method, you must first analyze the boundary situation of the object.

If it's a test score, it's from 0 to 100

First of all, look at the headquarters background management system, although the test of basic data is relatively simple, but it requires an understanding of the specific business, and the basic information is roughly divided into: business management, store management, commodity classification, commodity attributes, commodity management, warehouse management, location management, account management. Each of them is tested according to the corresponding design book, the basic data test is the simplest, of course, the most basic, only the basic data test can be carried out smoothly, otherwise every step in the back will be blocked.

Take the business management to a simple test, first test the new business, deletion, and functions, and then test the details, such as field length, character type, etc., according to the design book is much simpler.

The core part of the background management system of the headquarters should be the basic functions and logic of procurement, sales, warehouse, and capital to be tested, collectively referred to as purchase, sale and inventory, and I will explain in detail in another experience about the test of purchase, sale and inventory. As the name suggests, purchasing, selling, inventory.

3** business management system, mainly the sales system of the first business, divided into ordinary sales and direct sales, the business sales system is relatively simple, the logic is not so complicated, there is no problem with understanding, as long as the understanding is easy to measure, the business management system is used to be responsible for sales and returns, the whole system is two documents: sales orders and return orders.

4. The logic involved in the store management system is more, procurement, return and exchange, inventory, receipt and commodity management, compared with the headquarters system, it is simpler than the first business system, but on the basis of the headquarters system, the store system can be easily tested.

System Testing.

The system test is a black box test based on the overall requirements specification of the system, and should cover all the joint components of the system. System testing is a test of the entire product system to verify that the system meets the definition of the requirements specification and to identify areas that do not conform to or contradict the requirements specification.

The object of system testing not only includes the software of the product system to be tested, but also includes the hardware, peripherals and even some data, some supporting software and its interfaces. Therefore, it is necessary to combine the software in the system with various dependent resources and test it in the actual operating environment of the system.

"Test System" is a book published by Chemical Industry Press in August 2008. "Test System" introduces electromechanical and hydraulic testing and application technology. Firstly, the design of common sensor application interface circuits in electromechanical test systems is introduced.

This paper introduces the analog input and output channel structure and common chip interface of test data in the process of transmission with the microcomputer system, and illustrates the multi-channel patrol detection data acquisition system. The stepper motor test technology, driver circuit, and closed-loop control are described in detail. The testing principles and methods of electro-hydraulic proportional components and systems are introduced.

In the test system configuration and anti-interference technology, the reliability design and chip configuration design of the bus are introduced, and the protection and monitoring circuits composed of typical chips are illused. Finally, the general steps of mechatronics test system design are summarized, and the design process is illustrated for design examples.