Test points

    The current project has such a problem, and the test needs to be carried out by itself. In the process of the project, because the testing work was not done well, it brought too many troubles and problems to myself, so I have also written a lot of testing blogs recently. It will take a long time to complete the transformation.

    After reading a test plan, I think it is very good, and summarizing it in the blog is also a process of supervising my memory.

Chapter 1 outlines and explains the purpose of writing, which readers will play, project background, test objectives, and reference

materials . Chapter 2: Test configuration requirements

1. Network environment, network hardware environment: hardware topology, quantity, configuration, etc.; network software environment: name, Protocol, communication, connection method.

2 Server environment, server hardware environment: name, specification, quantity, configuration; server software environment: name, protocol, version, etc.

3 Workstation environment, workstation hardware topology, name, specification, quantity, configuration; workstation software name, protocol, version and other information.

4 Test methods, describe the test methods and tools, and the test record form must be filled out at the same time when the test is performed.

5 Test data, the test data must conform to the business rules provided by the customer, the requirements analysis specification, the outline design specification, the detailed design specification, and the data rule specification. Including operational restrictions.

6 Testing strategy, testing includes unit testing, assembly testing, and system testing. According to different development stages, the focus of testing is different.
Unit
testing is divided into systems, subsystems, and modules, but the final unit must be a functional module, or several subclasses in an object-oriented process. Unit testing is to verify the correctness of each function, and it is also the basic work of subsequent testing. The purpose is to find errors within each functional module. Therefore, it is necessary to write tests from the internal structure of the program. The key points are: module interface, local data structure, path, error handling, boundary.

Integration Testing
Also called assembly testing or joint testing. Usually, all modules need to be assembled as designed on the basis of unit testing. Need to consider: whether each module is connected, whether there will be data loss through the Mouai interface; whether the function of one module will adversely affect the function of another module; whether the combined sub-functions meet the expected requirements of the parent function; global Whether there is a problem with the data structure; whether the errors of the unit modules accumulate, and whether the method will reach an unacceptable level. One-time assembly or value-added assembly can be used. The purpose

of system testing is to verify whether the function and performance of the software and other features meet the requirements of users. The types are divided into: 1) User interface testing, testing whether the user interface has navigation, aesthetics, industry or company specifications, and whether it meets the design requirements. The requested executive function. 2) Performance testing, testing response time, food handling efficiency, or other time-sensitive issues. 3) Strength test, testing resources, including memory and disk sensitive issues. 4) Capacity testing, testing the impact of a large amount of data on the system. 5) Fault-tolerant testing, testing the ability of system software to overcome software and hardware failures. 6) Security testing, testing the ability of the software system to prevent illegal intrusion. 7) Configuration test, test the quality of the software system under different hardware and software configuration conditions of different networks, servers, and workstations. 8) Installation testing, the installation effect of the all-inclusive software system in all possible cases and the quality of correct operation must be guaranteed once installed. 7 Test Pass Criteria Chapter 3 Introduction to Software Structure, including Overview, Overall Function Module Introduction, Function Module Relationship Diagram, System External Interface Function Module Relationship Diagram, System Internal Interface Function Module Relationship Diagram Chapter 4 Unit test cases include system, sub- System Chapter 5 Integration Test Case System External Interface Test, System Internal Interface Test


















Chapter 6 System Test Case Virus Testing, User Interface Testing, Performance Testing, Strength Testing, Capacity Testing, Fault Tolerance Testing, Configuration Testing, Installation Testing, Security Testing, Regression

Testing Chapter 7 Traceability Table

Chapter 8 Appendix Approval Record Table