test early
Test early in the software development life cycle to find and fix problems before they escalate.
Any code/configuration changes need to be tested
Sometimes the code is submitted for development and changes, but the test is not told. When the test sees the code submission, it finds that there are changes.
The test feels that the change is simple, no test is required, no test.
Or I didn't understand what was changed, and I didn't bother to ask, and I didn't want to cause trouble for myself, so I didn't ask.
The unforeseen consequence is that there is no guarantee, because problems often appear where you think there will be no problems, so any code changes need to be tested.
Defects after verification in the test environment need to be verified again after release
Sometimes the defects verified in the test environment will cause problems again after the release, so it needs to be verified again.
Ask any doubts
During the testing process, any doubtful points must be brought up. Don’t be afraid that the development will think that you don’t know this, and if you question you, you must also raise it.
For some defects, you may not think they are defects when you first encounter them, but if you tell the development, you will get the answer instead of letting them go.
Test cases are designed first and then written
Whether it is functional testing, interface testing, performance testing, or test cases, they all need to be designed before writing.
As shown in the figure below, this is the process of test case design.
completeness principle
In test case design and execution, all scenarios and paths need to be covered to maximize potential defects and errors.
Principles of automation
Use automation tools and technologies to realize the standardization, automation and continuity of the testing process. Work that can be automated should not be repeated multiple times.
Pay attention to defects
It is necessary to pay high attention to and pay attention to defects and problems, record and report them in a timely manner, and work closely with the development team to confirm the priority and process of defects, resolve defects early and give feedback on test results.
Continuous Improvement Principle
Summarize the experience and lessons, evaluate the test effect and the use effect of test tools, constantly find and adopt new test methods and technologies, and improve test efficiency and test quality.
Principle of Stability
The test environment should be consistent with the production environment, the test data should conform to the actual business situation, and the test process should be stable and reliable.
No report no release
Test the report, and after the defect is repaired, send it to the project manager for confirmation and reissue. Avoid taking the blame for problems after the release.