Shulou(Shulou.com)06/02 Report--

The establishment of the testing process should be analyzed and set up according to the situation of the company's project and the current situation of the testing team, and should not only be imitated without innovation, otherwise the testing process will be difficult to move forward, or it will greatly affect the work efficiency. Can not play the essential role of testing. First, the traditional testing process (this testing process is suitable for the mature situation of the test team) planning stage: 1. Develop the test plan (premise: the development team needs to provide requirements documents, design documents, development cycle and release cycle). After the test plan is developed, the project leader needs to participate in the review to confirm whether the test plan is executable. Test phase: 2. Test cases (two cases: can be written according to the detailed design document, if there is no design document, can be written later according to the system) 3. Unit testing: unit tests are generally performed by developers (including smoke tests), and then unit test reports are written by testers based on the results of the tests. (Vu unit test tool) Visual Unit unit test Vu instructions: http://wenku.baidu.com/view/49191d262f60ddccda38a04b.html 4. Integration testing: (testers need to focus on learning) to write an integration test report http://www.51testing.com/html/22/n-7622.html (integration testing tool httpUnit) 5. System testing: including functional testing (manual and automated), performance testing (pressure, capacity, load, etc.), compatibility testing, regression testing, database testing, documentation testing, and so on. (the modules to be tested should be defined in the test scheme according to the requirements of the project.) write the system test report. The tester's work content and approximate schedule 1. Be familiar with the project requirements, design, cycle, etc., and then write the test plan. (one week) 2. When the documentation is complete, you need to start writing test cases. (two weeks-first draft) 3. According to the results of the unit test, write the unit test report (two days) 4. According to the integration test results, write the integration test report (two days) 5. Functional testing, performance testing, compatibility testing, etc. (4 weeks) 6. Write the system test report (3 days) 7. Regression testing, for the next round of testing. (two weeks) 8. user's manual. (week-first draft) 9. Online help. (two weeks) 10. Test cases, user manuals and testing work need to be continuously updated according to the progress of the project. Second, suitable for the department's testing process: (there are many projects, there are only two testers, in view of this situation, the personal recommended testing process is as follows) 1. Test outline: a test outline is required before the test starts, and each version of the test requires an executable test plan. two。 Test cases: mainly business processes and function points, do not need very detailed use cases for the time being, write a function list (on the one hand, it can be easily provided to developers as part of the acceptance document, on the one hand, it is convenient for testers to save time and improve usability) 3. System testing: the first is functional testing, and then other performance tests, compatibility tests, installation and uninstall tests are carried out according to the requirements of the project. After the completion of the system test, it is necessary to provide the test report and feedback to the developer. 4. Regression testing: after the next version of the project, you need to do regression testing and test the new function points and the modules associated with that function. (when there is plenty of time and the project needs continuous regression testing, automated regression testing can be promoted step by step) 5. Test report: after the beta version test is completed, you need to provide the beta version test report. 6. User manual: write a user manual. (write a user manual during testing). The tasks that the tester needs to complete (the time is about the expected cycle): 1. Be familiar with the project requirements, design, cycle, etc., and then write the test plan. (three days) 2. When the documentation is complete, you need to start writing test cases. (three days). Functional testing, performance testing, compatibility testing, etc. (five days) 4. Write a concise version of the test report and provide it to developers (one day) 5. Regression testing, for the next round of testing. (four days) 6. System test report (full) (3 days) 7. user's manual. (five days-first draft) 8. Online help. (ten days) 9. Test cases, user manuals and testing work need to be continuously updated according to the progress of the project. Testing also requires multiple regression tests based on the released version. Summary: according to the normal process, it takes about 19 working days to complete a test and regression. The production time of the user manual and online help can be interspersed with the testing process. Example (XXXX guarantee Service system): 1. Need to provide XX project design requirements, design, cycle documents, testers through the documents to develop a test outline; 2. Provide detailed design documents or systems, testers begin to write test cases; 3. After the system is stable, the functional test and performance test are started, and the test report needs to be submitted when the test is completed. After the developers solve the bug in jira, release the new version, the testers begin regression testing and the next round of testing, and submit test reports after testing; 5. After the system version is stable, write a detailed test report. 6. Then start writing user manuals, participating in project packaging, and installing and uninstalling tests. Third, establish the test knowledge base 1. Incorporate the learning plan into the work plan, define the time period, summarize the results after learning, and store the learning results in the collaborative communication platform. The advantage is: usually use the spare time to accumulate good testing knowledge, so that when there are related testing requirements in the later stage, the relevant testing can be carried out more quickly. two。 Skills I have collected for testing: web testing: selenium automation tools, AppScan security testing, Xenu link testing and other scripting languages: python, VBScript, C #, C database: Access, SqlServer, Oracle operating platform: Linux commonly used testing tools: QTP, Loadrunner testing technology: functional testing, performance testing, document testing, stress testing, compatibility testing, security testing, reliability testing, virus testing, Installation and uninstall testing, other: QC, network knowledge, bugfree, TeamCity, Visual Unit (Vu), HttpUnit (integrated testing tools) 4, some standards: 1. Test types: functional testing (first ensuring the correctness of the function), performance testing (unless you emphasize or want to verify whether specific performance indicators are met before performing performance testing), installation testing, interface testing, stability testing, reliability testing. two。 Test outline: each test project is required to write a test outline, according to customer requirements, according to customer requirements, according to internal simplified template (test scope, function list, test time, personnel arrangement, test environment), build a separate document to form a specification. 3. Test report: it is required to be the same as the test outline; the small version of the test results can be sent directly to the relevant personnel by e-mail; finally, the comprehensive report suggests that when the project is proposed for acceptance, it can be prepared in a more formal format. 4. Test duration: at least 2 rounds of centralized testing for each project (first test + regression test), at least two weeks before acceptance; no more than one week for each centralized test (including familiarity with system requirements and writing simple test outlines and test cases); 5. User manual: documentation that must be written; user manual recommends cross-testing; (avoid serious and obvious low-level errors)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.