Shulou(Shulou.com)06/01 Report--

4399AT UI automation CI and CD example analysis, I believe that many inexperienced people do not know what to do, so this article summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

First, take a look at the difference between CI,CD (continuous delivery) and CD (continuous deployment), as shown in the following figure:

After seeing the difference between the three, at present 4399AT has reached the stage of CI and CD (continuous delivery). Next, let's talk about CI and CD of 4399AT.

The following is based on the Android project APP:

Software: jenkins+gradle+4399AT+sonar+gitlab+tomcat+nginx

Language: json,python,javascript

Jenkins: need to download plug-ins email, gitlab,gradle,sonar, etc. Jenkins is the brain, need to guide every operation

Gradle: gradle for compilation, available computer configuration, and project configuration

4399AT: Android UI automated testing tool for automated testing and report generation

Sonar: for code review

Gitlab: used for code push and automatic build triggered by jenkins's webhook build mechanism

Tomcat and nginx: for the proxy address of the server, you can use tomcat on this route, but only the local area network. Later, the boss uses the domain name configured by anti-proxy, so that it will not be inaccessible due to different IP segments.

Json: for writing test case scripts

Python: for overall automated test execution, migration of test reports, judgment of construction reports and acquisition of some email parameters

_ javascript: for report generation

Test scenario:

Instead of building a test every time the code is submitted by CD (continuous) delivery (this has been tried, which is not suitable for our current model, mainly because we can't see the effect), but through an agreement with the developer to open several branches in gitlab, named after the environment, such as the test environment and the production environment, when the development function is completed and the self-test is completed, when the test email is sent and the code is pushed to the test branch, jenkins webhook will be automatically triggered directly Then it automatically carries out the automatic test of continuous build compiled code scan.

The following is a general flow chart:

The report implemented is as follows:

Effect:

The whole Prophase can solve the problem that the test package can not be installed or easily flickered. After the later use case is improved, we can carry out functional and traversal testing to reduce the amount of testing. in addition, we can adjust the test content in time according to the implementation, and focus on the risky modules.

At present, there is not a good assessment of how much efficiency can be improved, but compared with before, it can shorten the project cycle by about 10% and 20%. It is still in continuous adjustment and practice.

After reading the above, have you mastered the method of 4399AT UI automating the sample analysis of CI and CD? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.