How can I quickly join the test team as a new person?

Transferred from the Internet, the source of the article is unknown ......

As a test newcomer to join the team, in most cases, the project team members are enthusiastic and welcome, and actively provide support and help as far as possible, how to quickly familiarize themselves with the project business and test environment, I will devote myself to practical work as soon as possible. I will talk about my personal experience and some opinions for your reference:

1. Looking for new company team elders:

Generally, when a new employee enters a new company, a master must be designated for a period of time, which is what we call the testing predecessors. Many times, the testing predecessors are experienced and experienced testers. How can you get along well with him and have a good relationship? Based on his rich business experience, I will give you some advice, it may be better than you have tried it for 10 times. Many new testers are arrogant when they first enter a new company. Their eyes are high and low, and their predecessors are unwilling to submit the test. When the trial period ends, they are forced to leave the company and get fired. In this example, I can see 10 examples, but unfortunately many job opportunities are lost.

2. An empty learning attitude:

It is necessary to keep a modest learning attitude to a new company. I remember that when I first graduated, the company hired a test supervisor. He had 4 to 5 years of experience and experience was not simple. It was also a good guy in our mind. However, in addition to listening to the director's words, the person in our department is arrogant and has no one at all, I think the team is inferior to him. As an airborne soldier, the old employee and new employee are indifferent to him. When they encounter any problems and need the help of team members, they do not want to help him, the manager also talked to him several times, but the effect was not obvious. As a result, he stayed for less than two months. It is estimated that he felt very unhappy and was forced to leave the company. In fact, it is essential to maintain a low attitude and a modest learning attitude.

3. Read the project-related documents:

Generally, when a newbie arrives at the company, he or she will be arranged in the project. As a beginner in testing, quick reading of the relevant "requirement documentation", "Detailed design documentation", and "User Manual" is particularly critical. We can quickly familiarize ourselves with system-related knowledge and obtain relevant information about writing test documents through the requirement specification and other documents. If the user manual has been compiled for the project, you can familiarize yourself with each function step by step based on the steps in the document. Only by mastering the essence of these documents can testing become very easy.

4. Quick familiarity with project-related business knowledge:

If you are a tester at a new company and have rich experience in similar industries, you are familiar with the business. If your new company is an industry that you have never been in touch with before, you must work hard to buy relevant business knowledge. I have a deep understanding that I used to switch from a "communication company" to a "banking system" company. My business is completely different. I have a lot of business knowledge from scratch. However, if you have some work experience and learn quickly, the key is that you love learning and have a strong learning perseverance.

5. Get Involved in the tested system as soon as possible:

I just entered a new company. If the tested system has been developed almost, some functions are OK. You can deploy it in a test environment and try to get familiar with the system from the perspective of visual testing as soon as possible. Most of the time, the actual system operations through the page are much better than reading the document, and the impression is more profound, and the familiarity with the system is faster. If you join a company, try again.

6. Learn about similar products of the company:

Most companies cannot be very strong in every industry. Basically, they are very strong in a small field. The company is mainly engaged in R & D of products with strong related business. Therefore, there are a lot of related products. If the system you want to test has not been developed, if the time and conditions permit, you may first understand similar products of the company, so that you can get familiar with it as soon as possible. In most cases, many of the company's products are connected. Most of the products have modified some functions and interfaces at different customer requirements. I personally think: understanding similar products is also a shortcut for beginners to quickly familiarize themselves with products.

7. attend as many project meetings as possible:

In each project, especially in the project startup stage, the Conference will continue. In many cases, project team members complain that it is a waste of time and delay the development progress. If you are a beginner in testing, it would be great to join this seminar. Most of the time, the focus and key points of the project are discussed. If you disagree with each other, you must discuss the inconsistency in detail. Especially for business discussions, you can participate in several discussions, which is better than you can read 10 articles and have a thorough understanding. If you have some knowledge about the requirements, but some functional modules still have problems, you can submit them at any time during the seminar. We will discuss them and solve them together. If you have such an opportunity, do not give up.

8. Read the existing test cases for similar projects:

If the project has been started and enters the test phase, if you intervene at this time, the person in charge will usually provide you with test cases for the entire project or part of the modules that require your testing. These test cases are also important references for quick start testing. If you have not compiled a test case, you will be involved. You have to start over again. You can read test cases similar to the project and combine the testing experience of the previous project, write test cases based on the company-related test case templates. If you encounter problems that you do not understand and are difficult to solve during the preparation of the test case, you can enter the test requirement question form and discuss them at a department meeting. It is best not to ask a question if you encounter a problem. It is worthwhile to disturb people's ideas and get bored with others.

9. Check the existing defects in the defect database:

Generally, defect tracing systems classify software defects by modules. If the boss assigns you a test task, you can familiarize yourself with the module defects to be tested. After logging on to the system, filter the defects and try to follow the steps described in the previous bug test to see if the defects can be rediscovered? This method can learn from the experience of testing peers to identify problems as soon as possible to avoid testing blindness. One way, You can broaden your horizons to avoid submitting bugs of similar problems or duplicate bugs. The other is to help you quickly get familiar with the tested system.

10. You must understand who you lead:

When employees enter the company, there are many leaders in the company and department. I don't know who cares about me, but who asks questions? Who can help solve the problem? If this is the case, it will be troublesome. There are too many bloated department leaders. Some companies have two test managers, several test supervisors, and multiple project managers and R & D directors. They do not know who the work will return, owner. I am very tired of making every leader return !! My practice is: there is only one lead in the test project, that is, the test lead. The test lead is responsible for arranging and assigning the work and tasks of each tester. I directly review the test lead. If any problem cannot be solved in the project, members in the group can contact me directly, and I also regularly join the project to participate in some tests to learn about the progress of the test project, you need to talk to some people when necessary. In this way, the work report is simple, clear, and easy.

11. Familiar with the use of test-related management software:

I am talking about software related to this test, including missing test requirement management software (such as testdirector or QC), trap tracking management software (such as testtrack pro, testdirector, and so on) version configuration management tool software (CVS, VSS, or SVN, etc.). The degree of familiarity depends on your position. If you are a general engineer, you only need to understand the general usage. If you are a test Manager, you should not only understand the general usage, we also need to have a deeper understanding of software permissions and project configuration, because you need to be the admin of the software and most of the problems you encounter will be handled by you. high salaries are not so good, haha !!! If you are a new employee, you will not be able to connect to these jobs, you will have to put fuel on them. Otherwise, you will be familiar with the management software only when the test starts, so do you think you can quickly start the test?

12. Pay attention to communication skills and seize the opportunity to consult:

Communication skills are essential to familiarize yourself with the project and conduct tests as soon as possible. As a new tester, you should try to understand the modules and characteristics of each developer, find some common languages, and draw closer distance from developers, let them have a good impression on you. This is the only way to help you when you encounter problems. If you have a bad relationship with developers, you may find it annoying. They will certainly not help you, but do not intend to cooperate with you. When you make a mistake, they will seize these bugs and sometimes say that you don't understand anything. In this way, you will be very depressed, and you will definitely not be able to stay for a long time. You only have to leave the house. Especially when developers are very angry, you should have more understanding and tolerance, do not add fuel to the fire, you can give him some praise, give him some encouragement. As soon as he heard it, he always thought that you knew me the most and regarded you as your own. At this time, you may ask the developer a question, and his attitude may be different. He will explain it to you carefully and what will happen in the future, he will also be bored with helping you, because he feels that you know them the most and unconsciously treat you as a good friend and Buddy. In other cases, developers are free to visit the testing department. When preparing to communicate with you, they must seize the opportunity to joke with the developers and make some appreciation, it can also adjust the relationship with developers. In short, it is really difficult to do this. If it is done well, the effect is indeed different.