Panelists: Wangzhong Fei, Liu Rui, Xu Bao Bao, Zou Dongmei, Chen Zhiwei
- Discuss your test plan
Our project is based on a simple password management APP Android developers are written. We chose this project because, now more and more mobile phone software, each software will need to register an account and password, and the password if they would have the same set less secure, but different passwords will greatly increase our memories amount, and after a long period of time it is likely to forget, so there is a necessity of this software. The software is mainly used language or Java language, Java is now popular development language and a language we learn, so the use of the Java language.
- Do we need to test until our software is PERFECT?
Needs test is to find as many defects, such as functional errors, poor performance, user experience.
May be white box: the internal structure of the program visible, the logical structure of the source program testing and implementation details. White-box testing must be performed by the independent developer
Black Box Testing: invisible internal structure of the program, in accordance with the specifications to test procedures for compliance. Black box testing must be performed by an independent test team, because the developer is difficult to be objective.
Key findings the following questions: Is there incorrect or missing functions; on the interface, the ability to receive the correct input, can output the correct result; · Is there a data structure error or external information access error; is able to meet the performance requirements; whether initialization or termination error; black box testing need to determine all possible input and output conditions of the test data to check whether the program can generate the correct output; sometimes test data is too big, is not realistic .
Such as: When testing a module, white-box testing: To single-step tracking test all the code, is concerned that the internal details of the program. Black Box Testing: Just a test module interface is required, the real concern is the external current program.
- What is “good enough” for testing？
1, to fully consider the practical test plan, namely, the closeness between the planned and actual testing and maneuverability.
2, should adhere to the principle of "5W1H", a clear test content and process.
A clear test of the scope and content (WHAT);
purposeful test (WHY);
clear test start and end dates (WHEN);
explicitly given test documentation and software bundle storage location (WHERE);
task allocation clear testers ( WHO);
clear that the test methods and test tools (HOW).
3, using review and update mechanisms to ensure that the test plan to meet the actual demand.
Because software projects is a gradual process, the middle inevitably demand will change, in order to meet changes in demand, the test plan also need to make changes in a timely manner.
Why take the appropriate accreditation system is to evaluate the integrity of the test plan, correctness, feasibility, quality assurance testing.
4, test strategy to be described as a key test.
Test strategy is an important part in the test plan, test plan is a factor in a project's testing requirements, test methods, test personnel arrangements, from a macro,
make an inappropriate analogy, you can think of is testing the test plan expected output, and test execution is the actual output of the test work, the expected output! = Actual output
as for test work, I think we must first clear test case status and its role in the entire test work. Personally think, test cases throughout the test work in the
position and role is mainly reflected in the following areas:
1, the test is performed physical tests, and forms an important basis for test methods, test quality, test coverage;
2 , test cases are internal communication and cross-team test basis;
3, regression testing, there are test cases can greatly reduce the workload of the test, thereby improving the efficiency of the test;
4, the test case to facilitate the testing of tracking management, including progress tracking test execution, test the quality of the track, and workload tracking and evaluation testers;
5, before the completion of the test work carried out to prepare test cases, blindness can be avoided testing work carried out;
6, the best test is to convince users to believe based on product quality, but also It can be provided to customers as the basis for project acceptance.
When we recognize the status and role of test cases in the Lands and test work, I believe we have recognized the importance and necessity of the test cases for testing,
1, do project training testers (mainly refers to the demand awareness) job analysis, software design, test plan. To play all the capabilities of the team, the best way is to let every member of each of them are aware of all the details of this project, as well as their responsibility in this project to be undertaken.
2, as far as possible using conventional test other items; and similarly classify the project module, writing test cases by type, and then modified according to the characteristics of each module, to take full advantage of reusability of the test case.
3, under tight time resources, you can write the test in accordance with the critical path of test cases, test case for the critical path must be detailed, the other edge of the module test cases can be considered (both only true test certificate) only through testing.
4, for the preparation of test cases using modular. Personal recommendations will separate test cases and test data, test case steps should be mainly reflected in the test business processes, and test data is mainly reflected in the test results for the data processing system. Taking into account the changing needs of software project problems, it is recommended to separate these two, related through the number of test cases, in order to respond to changes in demand caused modify test cases, thereby reducing the amount of modification of test cases, shorten the project cycle, improve work efficiency.