Time flies, and it’s the third year of doing the test.

Think back to why I chose software testing in the first place, because I wanted to make the world a better place…

Well, the test threshold was relatively low a few years ago. However, in recent years, the company’s requirements for testers are becoming more and more high, more and more comprehensive, and will only point to point has become difficult. So testers have to step up.

One, advanced – automated testing

In fact, this step is also the inevitable way to go in the process of quality construction, in order to do a more efficient and effective test work. For example, the purpose of developing automated services is to improve the efficiency of regression testing, so that you have more time to focus on new functional testing.

So to develop automated services, don’t you have to write code?

Some might say, I automate as a tool. Yes, you can, but I personally find it more flexible to develop in code. Of course, ultimately, the company or business needs to choose the most appropriate landing plan.

Second, advanced – platform development

When you build automated services that are successful and truly efficient, then you have the time or ideas to achieve more.

For example, if there is some duplication in a business test, see if you can automate it. For example, if people think that the tool you developed is very useful and you can share it with more people, then you can consider building a platform to integrate the tool into it and make it easier for more people to use it directly through a simple interface without command line operation.

Here I would like to mention a performance test platform implemented by the company internally, through the package of Jmeter, the service platform. At this time, when we do performance testing, we do not have to bother to schedule pressure resources, we do not have to solve messy environmental problems and so on, which greatly improves our work efficiency, which is a very meaningful thing.

Therefore, the test development position, in recent years is also very hot, major companies have a large number of recruitment needs.

Iii. Platform

For platform, I personally think it is better to solve the problem of strong universality first.

The one feature I want to implement right now is the mock feature. According to my own rules, I can return the result of the interface’s response.

For the sake of having a mock service to work with, there are mock application services out there, such as moCO. But I also want to develop such a feature for the sake of learning.

As for the technology selection, WE plan to use Springboot and VUE, because this is also the implementation scheme adopted by many companies at present. The front end now also has a lot of relatively easy to use scaffolding, can help quickly build, and then according to their own needs to change. Springboot is not too new to me, because interface testing sometimes pulls the code to be developed and debugged locally.



That’s about it. It depends on how it works in practice.