What if the testing process is not perfect and the development is not active?

I checked the national software companies on Skynet 1000 More than ten thousand , Among them, the listed companies are 7 More than ten thousand , That is, proportion 0.7%.

Through this data, we can find , Most companies tend to be medium-sized or small in strength and scale , That is to say, the process is not necessarily perfect , There is not even a process .

The following figure intercepts two pictures of data for reference ：

Why point out this problem ？ The author is currently in second tier cities , Work 10 Experienced several companies in , Few companies make the process very formal and perfect .

The basic form is ： The combination of conventional waterfall mode and agile mode . Catch up function has been launched and reappears Bug, Common status development quick positioning problems are modified , Test take the time to test , Release online after testing .

So the conclusion is that the process is not important , It is important that everyone work together to solve the problem , Product fast online .

So here comes the question —— What to do if you encounter inactive colleagues in this process ？

I think this kind of problem is very common for colleagues who have worked for several years , On the one hand, for newcomers who have just come into contact with the test , There is no way to start .

So, my recent project experience , Simply talk about what happened , I hope you can read the same story , If you have ideas, you can leave a message in the comment area , Let's discuss common progress .

Working background

1、 This test involves 3 Project teams , Here are named project teams A、 The project team B、 The project team C , You can see here , When troubleshooting problems , There are a few obstacles .

2、 This work comes from the project team A Leadership of , It is also my direct leader .

3、 The test process of the whole test is like this ：

• System a Transmit data to the system b, System b To the system c;

• System c The operation returns to the system b, System b To the system a.

Testing process

Before you start the test ,A The leader found me , Tell me to test xx function , At that time, I asked ： Whether the process runs smoothly , Whether it can be tested normally ？ The answer has been run through 、 It can be tested normally .

I started to prepare for the test , After several steps, I found the system C After the operation is completed , stay A The system has no feedback , There may be A、B、C3 There are problems with both systems .

Find the relevant developer to confirm the problem , After simple communication, I pulled relevant personnel into a wechat discussion group , A long investigation has begun , There is actually another branch here ： Throw the problem to A Leader , Let her coordinate .

Why didn't I do this ？

The main reason is that my direct leader , The leader came to you to solve the problem 、 Dealing with problems 、 Sharing problems , Instead of saying ： The leader has difficulties and needs your help to deal with it .

If I had adopted this method at that time , Maybe nothing will happen later , And it has nothing to do with me .

In the early

C The group developers are very cooperative , Correct attitude ,B The attitude of group developers is not good ,A Group developers have been very active .

Start testing

Debugging probably 2 God During this period, I experienced many problems finding, development and debugging , because B Group developers belong to the warm water boiled frog attitude , Not very well .

node 1

I found B Team leader , Describe the process , The team leader also has other things , But I have tried my best to help debug , But in such a uncooperative state in the early stage ,C The person in charge of group development is emotional .

node 2

I feed back the question to B Team leader ,B The group leader continues to feed back to the leaders ,B Group leaders began to pay attention to .

At this time, there are development leaders of each group in the wechat Group 、PM And test .

node 3

After communication ,3 Group developers conduct internal joint debugging , The test is not involved .

Last , Successful joint debugging 、 Give it to the test 、 Test to verify .

Time estimate , From a test point of view , Tracking and coordination is at least a waste 2 Days time , But the result is that things are solved .

Sort out the mentality of different personnel

Through the above process , Summarize the psychological state of different people , The following table ：

summary

What experience can we learn from the whole process , It can be handled more efficiently next time ？

1、 When problems are found , If you think it's a big hole, you can transfer , But I don't recommend it .

2、 Once the problem is discovered , Find relevant leaders at the first time , Then the leaders assign it to relevant development , I was because the person in charge was at the customer's site , Try to solve it by yourself , I didn't expect to encounter a nose of ashes .

3、 If you can , You can participate in the process development , Personal experience is not the difficulty in formulating the process , The difficulty is that after formulating the process , How to better involve everyone , The skill and size here need to be handled properly ！

4、 Encounter uncoordinated development , Can be managed upwards , Ask superior leaders for support , Emotional is not recommended .

At the end

These materials , And the answer to the interview questions should be the most comprehensive and complete preparation warehouse for friends who do software testing , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful …….

I wish everyone can get the heart offer~~