The so-called "interview to build a plane, work to screw the screw". Let’s start with the first one, the interview. It’s like writing an article and making an outline first. You need to know the specific knowledge you need to learn in your industry to ensure the correctness of our direction.
1. Interview
The software testing (full stack), written test and interview methods summarized during the vacation, first look at the catalogue, which covers all the knowledge that needs to be learned to do software testing.
All of the above have been sorted out.
2. Ideas
Before deciding to self-study, you must ask yourself a few questions, and think about these questions clearly. The road to self-study will be much smoother, because I have seen too many "giving up from self-learning".
1. Do you really want to enter this industry? Is it really thought out, or is it just a spur of the moment because of the envy of the salary level in this industry?
Once you have figured out this question, you won't have to give up when you encounter difficulties in the later stage. You have to walk the path you choose, even on your knees!
2. Is there a strict schedule for self-study time? Is it possible to set aside time to study regularly, and this time period is not disturbed by other things?
If this problem cannot be solved, then it will be three days of fishing and two days of drying the net, learning from the front and forgetting the latter. After all, it will not be a system.
3. In the process of learning, it is necessary to combine the actual project to practice. Where can this project be obtained? Is there a stable channel around you to get in touch with the project?
If this problem cannot be solved, then the learning and use will be disconnected, and when you actually enter the enterprise, you will be completely confused.
4. How to solve the technical problems encountered in the learning process? Baidu? Ask your friends around you? Go to the chat group and ask?
I put this question at the end, and it is especially important, because all technical things are dead. Baidu questions are not comprehensive and not targeted; friends around you can look at their own situation, including asking for advice in exchange groups, but no one is obliged to help you all the time.
If you understand the above 4 questions, then where to start is a small problem, but I just let you think about the difficult problems you will encounter in self-study before you start self-study, so as not to encounter problems in the middle circled when. OK, let's talk about mentality.
3. Mentality
About self-study
1. It is easy to get started with software testing, but this is not the reason why you think it is easy to learn. It will despise you as you despise it;
2. The low threshold means it is easy to get started, but it also means that the road to climb is longer;
3. Reading a book cannot solve the problem, it is just a reference, the update speed of the book is slow, and the information conveys a single, but the classic is still a classic after all;
4. It is not easy to recommend self-study. It depends on the person. Self-study is very easy to get into the horns, and I have seen too many "giving up from self-learning".
About work attitude:
1. Think that software testing is to write test cases, execute them, summarize the bugs, and wake up as soon as possible, otherwise, you can only do a little bit for a lifetime. If you don't rule yourself, let others rule you;
2. At first, everyone around me thought that the test was easy and the money was easy to mix. After a few years, it would still be the same;
3. There is no end to learning, you work and others are also working, you are in a daze and others are learning, and then you will be fucked;
4. Don't have only imagination and execution at work, we have not grown to the point where the company cannot do without us;
5. Subjective initiative, take the initiative to contact technical content, adults should not expect others to chew things and feed you;
4. Skills
To study according to this roadmap, self-study will become very easy, and there will be no feeling of being unable to start.
Primary Stage
In the initial stage, four aspects need to be mastered
1. Basic knowledge of software testing, method of writing test cases and testing process
2. Master bug management tools, SVN and other necessary tools, as well as defect definition and test plan writing methods
3. Methods and protocols of web testing and app testing
4. Interface testing the operation and use of postman tools, basic knowledge of front-end H5 and CSS
5. Again, for example, learn the interface and understand the basic principles.
What are the parts of the interface?
First, the interface documentation should contain the following:
1. Interface description
2. Call the url flavor y
3. Request method (get\post)
4. Request parameter, parameter type, request parameter description
5. Return parameter description
If you are testing http interfaces, you need to call at least a library that sends http requests, such as httpclient to send different types of requests to the interface to be tested, such as GET, POST, PUT, DELETE, and bring your request w header And the request body body, and then use the xml library to parse the fields of the return value of interest, and compare it with the expected value to determine whether the use case succeeds or fails.
That is to say, the simplest interface automation has roughly three steps: a-send the request; b-parse the result; c-verify the result
For convenience, you should customize three business-related test classes:
1. A class used to encapsulate httpclient, used to send requests, used to send various test requests.
2. A class that parses the result xml to get the result value of interest.
3. A class for comparing test results with expected values, for validation.
Of course, this is the simplest http interface testing framework. If you want, you can do more powerful things, such as automatically generating test data, generating custom-formatted test reports, automatically sending test reports, checking whether the server-side data content is correct, etc. .