Software management process, the system testing phase includes functional testing, interface testing, compatibility testing, performance testing, security testing.
Some of the testing phase and the other phase is a strong relationship, such as smoke testing must be allowed to enter through functional testing, performance testing before entering the function test is passed, then how in each test phase to determine how to achieve the standards can be smoothly flow into the next stage it. Each stage of the admission test under quasi Here are the rules, but the actual work according to the project requirements, the nature of the demand for flexible configuration.
The basic function of the flow test are:
Start -> Needs Analysis -> Development and Design -> Test Plan -> Writing Use Cases -> Use Cases Review -> Application Test -> Smoke Tests -> Test -> Regression Testing -> End
Admission criteria for functional testing
1, the measured object has a separate testing environment
2, the test related documents have been updated (including project plans, test plans, detailed design, test cases, requirements specifications, features lists, etc.)
3, function measured mention inventory information clear, accurate self-test result data
4, smoke testing stage and severity found in the number of defects is less than 3 or more and is generally less than 20 defects grade
(Note: Some items need to be calculated according to the size, combined with thousands of lines of code to define defect rate)
A quasi-functional testing guidelines
1, the basic needs of the measured object and scope of the specification
2, no serious defect levels, and the general number of defects is less than 10
3, has refused, suspended, defects are properly treated
4, a functional test reports
Access Interface testing guidelines
1, interface test objects have been filed by FBI
2, the test has passed the static interface document (containing interface information, parameter passing information, the response information, etc.)
3, interface testing environment can be used normally
The criteria of quasi-interface testing
1, the interface has been fully covered and the list of features to meet the demand
2, the interface passes information has been strictly controlled, and no other problems
3, the interface has a test report
Access performance testing guidelines
1, we have provided performance test environment configuration simulated production environment
2, submitted to performance test function module must have been tested
3, "Application Performance Test" has been submitted by the static test (comprising: feature point to be tested, the reference index, the test scenarios, requirements, etc.)
4, has administrator privileges test server for easy viewing server resources
Application performance tests can be found in the following table:
Quasi out guidelines for performance testing
1, the scene has covered all business is completed, the indicators data have been documented
2, the test index information meets the test requirements of the application form or presumed to meet the needs assessments
3, has a "Performance Test Report"
Admission criteria for IT security testing
Safety tests also need to submit a "safety test application", the application through before entering the testing phase
Generally, if the professional security testing team will first provide a "safety testing program," the program is subject to the stakeholders in the review by.
Meanwhile, security testing program will test described in Notes, based on their written safety test ideas, output test cases.
1, "Safety Testing Application Form" and "security testing program" through the static test
2, includes a safety test application assessed testability
3, before safety testing, functional testing has passed
A quasi-safety testing guidelines
1, test scenarios covering all safety tests and test points scheme
2, the system has not detected or more general security issues
3, has a "safety test report."