1. What is software testing? What is the purpose?
Software testing is the process to run using manual or automatic means or measurement software system, its purpose is to test the software system meets the requirements, and identify the differences between the expected results.
2. Description of the process of integration testing
Upon completion of the software outline design, began to develop an integrated test plan - design integration test cases and test procedures - implement integration testing, design and driving piles required for integration testing - perform integration testing, record the test results - Evaluation integration testing, evaluation of the test according to the test results, generate reports to evaluate the document.
3. What are the white-box testing method?
Code review, statement coverage, branch coverage, condition coverage, covering composition, the basic path, formal methods, symbolic execution.
4. Description of the test target which type
Functional testing, performance testing, security testing, load testing, stress testing, compatibility testing, localization testing, installation testing, internationalization testing, reliability testing, usability testing, recovery testing.
5. How do the test documents?
The main test document using the static test, and go check the method, is based on peer review, listed in a checklist, and then we sit down to read the document to be tested against the troubleshooting. These documents usually very long, and the general advice is a peer review of time can not be more than two hours, it is possible to perform tests on the document to be tested, listed a plan, the total decomposition of the document, according to the plan several times on the document to be tested conduct walkthroughs.
6. What is the end of the test criteria?
From the look of the project cycle:
It exceeds the test time allocated;
Exhausted test resource allocation;
Reached a milestone in a fixed (such as the delivery date specified in the contract).
From the testing point of view:
Test coverage requirements;
Test code coverage;
Test metrics;
Defect inspection measure.
7.Alpha difference between testing and Beta testing
Alpha testing is testing in a development environment by the user, can be controlled internal test performed by the user in a simulated real operational environment, Alpha test can not be completed by the programmer or tester. Alpha testing found errors, you can immediately feedback to the developers at the test site, timely analysis and processing by the developer. The purpose was to evaluate the software product features, availability, reliability, performance and support. With particular emphasis on the interface and features of the product. Alpha began again after the test can begin after the end of software code, or the beginning of the module (subsystem) testing is complete ,, can also confirm that the product testing process to achieve a certain degree of stability and reliability. Related manuals, etc. should be ready before the Alpha test.
Beta testing is to test the software's multiple users in one or more of the actual use environment, developers often not on the scene.