I'm going to focus on coupons 591q.cn
What test, what order tests to cover what needs be aware of. Test case writers not only to master the software testing techniques and processes, but also on the tested software design, functional specifications, user trial scene and the procedures / modules have a more thorough understanding of the structure. Test case design generally comprises the following steps:
1, Test Requirements Analysis
From the software requirements document, identify needs to be tested software / modules, through their own analysis, understanding, finishing testing needs to be clear what function test object has to be. Features test requirements are: include software requirements, with testability.
Test requirements should be in demand software on the basis of induction, classification or subdivision to facilitate test case design. Relationship between test set and test the test requirements is many to one relationship, that one or more test cases corresponding to a set of test requirements.
2, Business Process Analysis
Software testing is not a simple black box testing based on functional, but also need to test the internal logic processing software. In order not to miss test points, requires a clear understanding of the software product business processes. Recommendations before making a complex test case design, to draw up the software business processes. If the design document business processes have been designed to complement the existing flow from the test point of view. If you can not get the business process from design, test engineers should, through the exchange of design documents and reading the developer, ultimately draw business process diagrams. Business process diagrams to help understand the logic and data flow processing software to guide test case design.
From the business process, the following information should be:
A, what is the main flow
B, flow alternatively what condition
C, what is the data flow
D, what are the key determination condition
3, test case design
After completing the test requirements analysis and software process analysis, began to design test cases. Type design including functional test, boundary testing, abnormal testing, performance testing, and stress testing. Design In one embodiment, in addition to the function test, a boundary should be considered abnormal, performance situation, in order to find more hide.
Black box test case design are: equivalence partitioning, boundary value, cause analysis and error guessing FIGS, white box test case design are: statement coverage, decision coverage, condition coverage determination / condition coverage, covering multiple conditions. Here we focus on black box testing. In the design of test cases when you can use the software test case design method, combined with the previous requirements analysis and software design process analysis:
Functional Test: test meets the definition of a function of demand, the function is correct and complete.
Suitable techniques: a functional test derived from the business requirements and design, equivalence partitioning
boundary testing: test the boundaries of the case of a function.
Suitable techniques: boundary value
abnormal test: on certain features, its border situation simply can not understand, or some operation is not entirely correct but is likely to occur, such a situation need to write similar abnormalities associated test .
Appropriate technology: the business requirements and design specifications special export an orchestration of error guessing method, boundary value analysis, internal boundary value testing,
Performance Test: Check whether the system meets the requirements as specified achieve performance, performance mainly to understand the procedure internal and external performance factors. Internal factors include the properties of the test environment configuration, system resource usage; external factors include response time, throughput and the like.
Appropriate technology: the business requirements and design specifications derived test
Stress Test: Stress test, also known as strength testing, mainly to check the ability of the system operating environment software running under extreme circumstances, such as to a considerable load or network traffic to the application software compatibility testing: test software compatibility features of products in different versions on different platforms, different tools, the same tools.
4, the test case review
after completion of the test case design, test procedures and methods in order to confirm whether correct, whether there are missing test point, test cases need to be reviewed.
Test case review by the general arrangements for the test leader, attended include: test case designer, test leader, project managers, development engineers, test engineers of other related development. Test case review is completed, test engineers, according to the assessment results, modify test cases and record the change log.
5, perfect test case update
After completion of the preparation of test cases need to constantly improve, the software product's new or updated requirements, test cases must be matched modify the update; ill-considered when designing test cases found in the testing process, the need for test cases revised and improved; software defects in software delivery after customer feedback, and the defect is caused due to loopholes in the test case, test cases need to be improved. Generally small changes can be modified to improve on the original test document, but the document must be changes. Version of the software updates, test cases generally should be followed by the preparation of an updated version of the upgrade. Test cases are "live", constantly updated and improved in the software life cycle.