1. The definition of software testing:
The process of using manual or automatic means to run or test a system. Its purpose is to test whether it meets the specified requirements or to clarify the difference between expected results and actual results.
Baidu Encyclopedia Definition: Software Testing (English: Software Testing), describes a process used to promote the correctness, integrity, safety and quality of software. In other words, software testing is a review or comparison process between actual output and expected output.
The classic definition of software testing is the process of operating a program under prescribed conditions to find program errors, measure software quality, and evaluate whether it can meet the design requirements.
2. The purpose of software testing:
Testing is the execution process of the program, the purpose is to find errors.
Ensure that the product fulfills its promised or announced functions
Ensure products meet performance and efficiency requirements
Ensure that the product is robust and adaptable to the user environment
3. The significance of software testing:
Free programmers and after-sales service personnel
Software testing can reduce software quality risks and enable programmers to concentrate more on the algorithm and efficiency of the program; at the same time, the
complete product that has been strictly tested also reduces the workload of after-sales service personnel.
4. Software testing process:
demand analysis
Develop a test plan
Design and write test cases
Implementation test
Submit a defect report
Generate test summary and report
5. Test flow chart:
Unit testing focuses on testing each program unit implemented with source code to check whether each program module implements the specified functions to ensure that it can work normally.
Integration testing is to assemble the modules that have been unit tested for testing, and the purpose is to check the program structure problems related to software design.
Confirmation testing is to check whether the developed software meets the various functional and performance requirements determined in the requirements specification, and whether the software configuration is complete and correct.
The main task of system testing is to incorporate the validated software into the actual operating environment and combine it with other system components (such as databases, hardware, and operators) for testing.
Acceptance testing is the last step to verify software products. In this link, testing mainly starts from the perspective of users, and the participants are mainly users and a few program developers.
6. Test workflow:
(1) After the product personnel have designed the prototype and documentation, a demand review meeting will be held. The participants include development, testing, and products. After the requirements review, a complete prototype and requirements document will be produced.
(2) The person in charge of the test team needs to develop a test plan based on the requirements document, project cycle, project characteristics, tools, and personnel arrangements.
(3) Testers start to write test cases (smoke test cases and ordinary test cases are required), and some questions will arise during the process of writing test cases. They should be confirmed in time with the product personnel and asked to return to the requirements document. (Development begins with outline design and coding).
(4) After the tester completes the use case, organize the test case review. Participants include development, testing, and products.
(5) Wait for the development to submit the test version, and perform the smoke test first after submission. The results of the smoke test require emails to inform relevant people, development, testing, and products. The most important ones are development leaders, test leaders, and products. Smoky does not pass and waits for the development to resubmit the version, but Smoky passes and enters the execution use case for testing.
(6) Some problems will be found in the testing phase, such as unclear requirements definition and conflicts in business logic. It is necessary to communicate with relevant personnel and clearly define them. After the conclusion is reached, product personnel must be required to update documents.
(7) After the module test that everyone is responsible for, cross-testing will be carried out within the team (some performance tests will be carried out at this time).
(8) Submit the product for acceptance after passing the test. Assist in product acceptance during product acceptance.
(9) After the product acceptance is completed, the project deploys a simulation environment. At this time, an online account is required, so it is usually the product and business personnel acceptance. The situation of each company is different. Some testers will be assigned an account to perform the basic process of the test (details depend on the company's situation).
(10) The simulation environment is ok, and the deployment is online.
(11) Some companies start from the time when the test environment is submitted for acceptance, and will ask to write some documents such as operation manuals, and some test reports, such as bug statistics and bug coverage.
7. According to the development stage, which types can be divided into? According to the test methods to be divided into several? Tests are divided according to technology, which types can be divided into the same category?
Unit testing, integration testing, system testing, confirmation testing, and acceptance testing are
divided into manual testing and automated testing.
Black box, white box, and gray box
Click the link to join the group chat [Python automated testing exchange group]