Software Performance Test Notes

1. Performance testing is often related to applications, operating systems, database servers, middleware servers, network equipment, and so on, positioning problems are difficult, how to quickly and effectively locate and solve performance problems, is an important task for performance testers.

2. Software testing classification, testing process, performance testing technology

3. Use of LoadRunner

4. Complete performance testing scenarios, plans, use case design, performance summaries, related deliverables documentation

5. The basic process of performance testing: Performance test requirement analysis, performance test plan, performance test case, test script writing, Test scene design, Test scene running, scene operation monitoring, running result analysis, system performance tuning, and test summary.

6. Debugging techniques such as script recording, load (scene design, execution), result analysis, breakpoint setting, single step tracking, log output, etc.

7. Monitor the performance of processes, CPUs, memory, disk I/O, etc.

8. The application process of LoadRunner in performance testing. including model establishment, performance test case design, Tool introduction, script code writing, scene design, performance analysis and so on.

9. Front-end performance testing, as well as front-end performance test analysis tools HttpWatch, DynaTrace Ajax, FireBug, YSlow.

10. Functional test Tools QTP, WinRunner, Jmeter

2. Software = program + documentation

   Program: A collection of instructions that implement a function

   Documentation: A collection of various types of graphics generated throughout the software's life cycle. Including "User Requirements Specification", "Demand Analysis", "System Summary Design", "system detailed design", "Database Design", "User operation Manual" and so on.
   

4. Software defects: computer hardware, software systems, application software errors.

   Hardware error, Reason: 1. Design error 2. Hardware Component Aging failure

6. Software life cycle: From the definition of software requirements, to the life cycle of being discarded.

8. Software testing is the process of reviewing the software requirements documents, design documents, the final product of the code implementation, and the user's operating manual in the pre-operation stage.

10. Software testing is the activity of performing multiple sets of test cases to identify software defects.

12. A test case is the smallest entity that performs a software test.

14. Software testing also needs to consider the test environment. Including hardware environment (PC, laptop, server, small machine, mainframe), software environment (operating system, Web application Server, database), network environment (LAN, metropolitan area network, Internet, LAN is 10MBIT/S or 100MBIT/S, etc.).

16. Test environment Construction, need to note: 1). Try to simulate the user's real Scene 2). Clean environment (avoid interference with other software) 3). Independent test environment (test and development environment should be independent).

18. Various classification structure diagrams for testing

    Performance testing: Performance testing, load testing, stress testing, capacity testing, concurrency testing, configuration testing, reliability testing, failure testing.
    

    650) this.width=650; "Src=" Http://s1.51cto.com/wyfs02/M02/82/41/wKiom1dPpFPyKNrmAATvsx7pPkA045.jpg-wh_500x0-wm_3 -wmp_4-s_1317478714.jpg "title=" capture. JPG "alt=" Wkiom1dppfpyknrmaatvsx7ppka045.jpg-wh_50 "/>
    

    
    

20. Black box test, the randomness is relatively large. An official US statement: 20% of the problems were found during the development process, and 80% of the problems were found during integration testing and system testing.

22. White box testing, focusing on the internal structure of the program and algorithms, usually do not care about functional and performance indicators.

24. Gray box test, based on the external performance of the program at the same time and the internal logic structure of the program to design the use case, execute the program and collect internal path execution information and external user interface results test technology.

26. 
    

Software Performance Test Notes