As a software test engineer, I can't breathe a sigh of relief when I get the offer, because there is a trial period. If you don't do a good job in the first project, you probably won't pass it. Test veterans have practical work experience and can calm down a little. Novices, especially those who have just come out of the training class and have a certain amount of packaging on their resumes, should be careful not to reveal their secrets. Then, from the first day of employment, to getting the actual project requirements, to completing What will happen in a project test?
1. Familiar with the environment
When I first joined the company, I didn't recognize everyone, and I didn't know who to turn to if I had a problem. What should I do?
First of all, when you join the job, the person who will definitely introduce you is the person in the test team. First, identify your leader, and then get along with the same table. Everything is easy to talk about. As a test engineer, the person who must deal with is the product manager. Manager, the development and testing of the same project team, inquire about the responsibilities of each person. It is difficult to identify people at the beginning, at least remember the name of the person on the company’s WeChat and match the position;
Ask the leader about the project that is most likely to be handed over to you next, and then go to understand the product information related to the project. For example, if you want to test the second phase of a large project, or an update iteration, then you First of all, we must understand the main process of this large project, and then have a more detailed understanding of the modules related to our own needs;
The next step is to be familiar with the various tools used by the project team. For example, if the data is oracle, you need to install PL/SQL first. If it is mysql, you need to install navicat first, and be familiar with their basic usage, and then figure out the project. Where are the relevant management tools and requirements placed? Is it on svn? Where is the prototype? Where is the use case written? How to record bugs, etc., you must first be familiar with the corresponding things, and then you will be able to do your job with ease when you start the work later.
2. Received specific project requirements
One: Familiar with the project background
The leader has clearly assigned you which project to test, so you must first be familiar with the background of this project, know who it is for and what problems it solves, if it involves some very professional knowledge, for example, if you join a securities company The company is working on a fund liquidation system. Well, first of all, you need to understand the basic knowledge of funds. You don’t need to go deep into it for the time being. Let’s figure out some basic concepts first, so that you can understand the project requirements. The functional points that will be actually tested later Learn more carefully.
Two: Familiar with the business
Find out what the main business of this project is, what is the process like, what functions does each business module have, how to interact with the database, etc.; to obtain this information, you may need to participate in the requirements review meeting. If you have missed it when you join the job, Then obtain it based on existing requirements, prototypes and other materials, and you also need to ask product managers, developers, etc. more.
Three: Analyze test workload and time points
When the leader hands over this task to you, he will definitely ask you how long it will take to complete it. Don’t rush to answer, first figure out the final delivery time point, and then roughly make a test plan, analyze how long it will take to extract test points, and how long it will take to write test cases , When will the development be tested? How long does it take for me to take a round of testing after the test? Because I don't know the quality of the developed code, it is best to estimate the time for a few more rounds of regression testing. Is interface testing required? Is performance testing to be done? How big are these workloads? After making a rough plan, you can share the plan first and let colleagues review it for you. If there is no problem, then give your relatively accurate time point. Don't boast too much, and you will not be able to finish it on time in the end, which will affect your impression.
3. Start writing test cases
As a test engineer, the two main tasks of work are to write test cases and execute use cases. The specific method of writing test cases will not be described in detail. It is recommended to check the style and granularity of use cases of other colleagues. The test manager evaluates your work ability, which may be Starting from evaluating your test cases, first of all, whether your use cases can fully cover the requirements, whether the title is concise and clear, whether the steps are clear and executable, whether the use cases are independent are all important, and there is also the problem of granularity. If the company It is required to write very detailed, then you can just follow it. If everyone is concise and you write too detailed, then the workload will be greater than other colleagues, which may affect the final efficiency, so you must observe carefully.
4. Tested
Before testing, you must first ask your colleagues whether you need the testers to deploy the test environment by themselves, whether to use linux commands for remote deployment, or to use jenkins to build directly. Then it's not just a matter of overtime.
Smoke test: Be sure to do a smoke test first, that is, run the main process. If the main process fails, and there are all 404, 500 and other problems, call back directly. If you just joined the job and don’t know the details Operation, if you are afraid of offending others, tell the leader first and ask her to operate it for you once.
Formally execute system test cases, record bugs if there are bugs, and then track and manage until no new bugs are found.
5. Test report
Summarize the test report based on the test plan, use cases, and bugs, and just ask colleagues to imitate the one they wrote before. The most important thing is the first project. You must take the initiative to make some summaries, such as your understanding of the business, which technologies you use, what difficulties you encounter in your work, how you solved them, what progress has been made, and what progress do you have for your current work? If there are any summary of improvement suggestions, send it to your leader to let her know your work ability.
After completing a whole project, I have clarified the company's work process and the work contact with relevant personnel, so I don't have to worry about becoming a full-time employee later. I wish all my friends smooth work and rising step by step.