For a long time didn’t update articles, UI automation process continues, recently has been planning for automatic platform, refer to other companies test platform is more of the UI to make keyword driven automation, but the effect seems not obvious, although the cost will be greatly reduced, without too much effort to open training can let the whole test team use; However, the disadvantages are also obvious, such as the large keyword use case independence, data-driven management issues, and the disadvantage of logical processing. A simple example is the RobotFramework, a powerful keyword framework that fails to solve the problems of complex logic. Finally, it is decided to carry out programming learning and training, and integrate test cases with modular call, with TestNg, SeleniumGrid and Docker assisting. The final platform only shows the choice of browser, and execute test cases on different browsers according to the choice.
The most critical thing is Docker’s auxiliary, powerful virtualization function, and the automatic operating environment and dependency package in a portable container, which perfectly solves the compatibility test of different browsers. Back in the early days of automation, dense piles of code were written from beginning to end; From encapsulation, data management, multi-threading, remote execution, test report customization, execution logging, and so on, I have climbed out of numerous pits along the way to Docker. It’s not the end, it’s not the end, it’s a long way to go, and it’s not something that anyone who sneers at the simplicity of UI automation can understand. In the future, still the same two words, come on. ——————— Author: Rain ink xuan mark Source: CSDN The original:Blog.csdn.net/ouyanggengc… Copyright notice: This article is the blogger’s original article, reprint please attach the blog link!
