Talk about testdeploy

This design , It's geek time 《 software test 52 speak 》 It's based on Docker Realized Selenium Grid Test infrastructure inspiration . In essence, I want to use the means of operation and maintenance , Rather than the means of development , Standardize the process 、 automation , Including environment deployment 、 Project specific tests . Build a common framework based on Testing Technology , Let's deploy 、 Special tests are carried out according to the set process under this framework .

We can see , The development process of test script is similar to that of business code . The test script is an introduction , If you don't understand, you don't understand , In fact, there is no need to say that we should understand all the tests , After all, industry specializing in surgery . Now there are some automated test platforms on the market , The output benefit is relatively low , In addition to investing manpower to develop and maintain automated test platforms （ Various technology stacks ）, And iterating over the script version .

For engineering practice , Methods are better than tools , Convention over configuration . If you use it directly Jenkins As a unified management platform , There are at least two obvious effects ：
（1） Can write scripts （ Such as test developers 、 Automated testers ）, So just iterate over the script directly , Just put more effort into designing use cases , Enterprises do not need to spend more energy and cost to build a use case management platform ;
（2） I can't write scripts （ For example, product personnel 、 Functional Tester ）, Just know directly in jenkins Just build on , After construction , It means that the automatic implementation of the project is over , The return to the project is completed .

k8s Under the architecture , Iteration of each version , Just update the service , It's actually updating the code . that , So is the test , We only care about the change of test script under version iteration , Iteration of each version , The test script code can also be iterated . There is no need to pay too much attention to the construction of the platform , because Jenkins It is our unified management platform , The function inside , I believe it is quite complete . indeed ,Jenkins Sacrifice in operating experience , But we pay more attention to the realization of assembly line .

At the end of the day , It is to use the idea of operation and maintenance to realize the technical architecture , And realize the automation of non core links as much as possible . For example, when the slave is added to the test cluster , Just add it to the configuration , Run the script , You can complete the environment deployment and initialization of the slave , There is no need to log in to the new slave terminal for manual execution to get the environment that the automated test and pressure test depend on . This also ensures the consistency of the environment . Many core functions , It is also left to a third party to complete , This is just a docking , For example, interface automation is popular HttpRunner frame , The distributed performance pressure test uses Locust. In terms of selection technology , Try to keep the cost as low as possible 、 Easy to use 、 Popularization 、 Those with strong universality .

Single Jenkins As a unified management platform , As projects grow , No doubt it will be the easiest to meet the bottleneck first . follow-up , Will upgrade TestDeploy, Realization Jenkins Cluster management .