The test engineer's workflow is related to factors such as the company's overall workflow, the test requirements of the project. This paper mainly discusses the general workflow of test engineers. Prepare for test 1) Clear test documents for test tasks usually include test purposes, test environments, test methods, test cases, test tools, etc. The test engineer must first read the document, form an overall understanding of the entire test, clear test purposes, and test requirements and test key, clarify the software test method and test tools. 2) Clear test time to clear the test cycle and test time progress. If you have a multiplayer to complete a software, you must first clarify your own test content. According to the test content and test cycle, you should estimate your own workload should be done every day. In addition, due to software testing is a group collaboration test activity, it is necessary to clarify which test contents can be collapsed with other test engineers. 3) Setting the test environment According to the test documentation requirements, set the software and hardware environments that test needs, including the operating system, software to test, and other necessary test tool software, etc. After all of these are completed, run separately, see if it can run correctly, and ensure that the test environment that meets the test documentation. 4) Learning the test software for unfamiliar software, you can learn the general operation of this software by reading the software yourself and help files, and learn the relevant book information, etc. In addition, ask other colleagues who are familiar with test software, and a shortcut to learning software. The more proficient in software, the more smooth testing process, the more ideal. 5) Confirm that the most important requirements for test task software tests are to identify test tasks and requirements, including correctly understanding the test document, confirming that the test can be completed according to the test progress. For test tools to be installed correctly, skilled. If there is anything you don't understand, ask the software test person in charge. Don't take your own understanding and subjective speculation, yourself. Of course, in the real test, it is often encountered various new small difficult problems, but also needs to ask the test person in charge to ensure smooth testing. Executive Software Test Task 1) Be carefully test according to the test document test according to the test documentation requirements according to the test documentation requirements, follow the test steps. By running the software, observe the test results, compare the contents of the software demand manual, find out the software error. For tests that need to call test cases, the test case is properly called, pay attention to observation and analysis of test results. Some errors that are not easy to repeat, need to be repeated, summarize the test steps you need to repeat the error until you confirm that you can repeat. 2) Record the wrong mistake, fill in the software problem report to correct the error in the software, the test engineer should correctly record the discovered errors, write the error reproduction step into the test report, the test report is an important part of the program test, correctly writing correctly The test report is the basic requirement for test engineers. The software defects found in the software defect database management test, each error as a record of the database, easy to record, modify, and query. 3) Fill in the test schedule and the necessary test content record table to write the test content to the test schedule per day, allow the test person in charge to understand the test progress, control the continuity of the test cycle, enhance the test process control, and ensure test Normal performed. Test records should be accurate and complete, seeking truth from facts, inserting test comments, interpreting special issues in testing. Test schedule is an important voucher for evaluating test quality and work content. For test errors and mistakes found after testing, you can find the cause of the error by checking the test record.
