Software test Case Design practical experience _ Test Tools

The most important prerequisite of software test case design is to master business knowledge and test case design method, the work of software testing is very simple, and more tests of several actual project skills will naturally improve. 　　I divided the software test case design into 4 parts: • Test type • Design idea • Design Technology • Chaff test type test Type There are many classifications, for the convenience of writing documents, you can combine various classification methods as a directory for use case documents. Clear test types can avoid significant leaks. • Document testing: requirements, design, user manuals ... · Interface testing: CLI, WEB, GUI, API Protocol conformance testing: consistent with standards. · Functional testing: To request documents, command/interface display functions, user manuals for writing clues. · Performance testing: Capacity, time, throughput, connectivity, and other results, including stress testing, load testing. • Networking testing: Some complex network protocols apply. • Integrated testing: Multiple modules or the entire system stack test, test the interface between the various functions are normal, whether or not each other. • Compatibility testing: Different manufacturers, Related products, different versions work together. • Event Testing: Modify configuration, reboot, power outage, etc. · 　　Security testing: Attacks, various anomalies, illegal testing • Stability testing: Analog online environment, long run. • Reliability testing: Mature, fault-tolerant, easy to recover. • Usability testing: Software products are understood, learned, used, and attractive to users. • Serviceability testing: Easy to analyze, easy to modify, easy to test, easy to manage. 　　• Portability testing: Migrating from one environment to another. 　　Divergent thinking and reverse thinking are the most important two thinking in the design of test. 　　The specific use of reference: XXXX Design Technology in the previous step or after the execution, can run common design techniques: • Equivalence class Division • Boundary value • False inference • Causality diagram .... 　　Chaff good enough to do, reduce use cases, prioritize. • Which features are features of the software. • Which features are most commonly used by users. If the system can be sold in chunks, which feature blocks are most expensive to sell. • Which feature errors will result in user dissatisfaction or claims. • Which programs are the most complex and error-prone. • Which programs are relatively independent and should be tested in advance. • Which programs are most likely to spread incorrectly. • Which programs are the performance bottlenecks of the system as a whole In. • Which programs are the least confident of developers.