Some testing prerequisite documentation and concepts to master are the most basic
1. Test classification:
According to the test technology, it is divided into:
Black box testing: that is, functional testing, which is what we commonly call the dots, but don't simply think that this is the case, the premise of the dots is to understand the business of the entire project
White box testing: You can see the code of the project, tests that belong to the logical structure
Gray box test: between black and white
According to whether you need to run the code, it is divided into:
Static testing: Mainly focuses on the interface
Dynamic testing: Run the code and enter the data
According to the software features, it is divided into:
Functional testing: Verify that all function points are as expected by the product
Performance testing: load testing, stress testing, database capacity testing
2. Test the process
Requirements review, project initiation - technical review, decomposition architecture - use case review, requirements alignment - decomposition of business, execution of testing
3. Test requirements analysis
This is the first priority, a tester to have enough understanding of the project, so to speak, the most clear understanding of a project in addition to the product, is the test, to learn to disassemble the needs, improve their business capabilities
4. Test plan
Generally large companies will have a standard test plan, we do not have Oh, however, the test plan is based on the requirements analysis of the test manager to write, the tester according to the plan to test
5. Test cases
There are many test case methods, such as equivalence classes, causal diagrams, boundary values, orthogonal arrangement, scene method, and generally companies will have their own set of use case specifications, find colleagues to template
6. Test review
Test review includes demand review, test plan review, test case review, before some of the attention points for test cases have a special article, interested partners can go to see
7. Defect management process and specifications
A bug will have a life course after the new submission, so it is divided into several states, with tools to manage the process of repairing the on-line, like many management tools on the market now, like Zen Tao, bugout, can be learned according to the company's requirements to master
8. Database
Database is also a focus of the test, the previous article is about mysql installation and some basic syntax, because it is a daily test, so master the basics, interview, written test may ask more, the actual application is not much
9.Linux
An operating system, look at the project, mainly master the common commands, can install software
10. Perform the test
System testing: Test the project as a whole according to the test case system, follow up the bug fix status, and ensure that it is online
Regression testing: After the project is launched, it is necessary to return to the whole again to avoid omissions, sometimes, the environment is also a pit, the environment will affect some functions, so the regression test, mainly in the use case before the problem is found to eliminate the problem as soon as possible
11. Test report
After the test is completed, a summary of the existing test situation, email, documentation, see the specific requirements
12. Mobile testing
For APP and H5 page projects, real machine testing is essential, and it can be compared with PC to learn
13. Compatibility Testing
PC compatible: browser kernel
APP, H5 compatible: mobile phone system, browser
For compatibility, large features will not have an impact, mainly some style display and foreground interaction issues
Automated testing is mainly used in more mature projects, basic page structure, framework design will not have major changes, learning costs and maintenance costs are larger, at present, they have written out the approximate framework, but the project is still in the early stage, and the later stage will always be maintained
Recommended tool: selenium+testng
Recommended language: Javapython
Because the work is not long, I have not yet been exposed to interface testing, but interface testing is a direction that must be learned
Some protocols, request methods, and packet grabbing tools, status codes to be proficient
Whether a website can carry the number of visits from users and what the carrying limit is the focus of performance testing
Recommended tools: LoadRunner, Jmeter
After reading this article, I firmly believe that the following two things will also help you improve yourself:
1. Like it so that more people can see it, and your recognition will also encourage me to create more high-quality content.
2, to make yourself stronger: think, if you are going to test the industry for a long time, your work experience and testing technology is absolutely not enough, you need to improve, you need to enrich your technology stack! What are you waiting for!
Finally: [Tutorials that may bring you help] (private chat q1 collection)
These materials should be relatively complete for friends who do [software testing], and this kind of learning materials have also accompanied me through the most difficult journey, and I hope it can also help you! Everything should be done as soon as possible, especially in the technology industry, and we must improve our technical skills.