Automated Smoke Testing

1. Smoke Testing and Smoke Testing. Because the company has been using the smartrobot tool, what we have been doing is product adaptation.

2. There are indeed some defects in Android mobile phone automation. automation cannot be missing in testing, but it cannot be replaced by manual automation.

3. All of our automated tests are based on the UI. As you can imagine, the great change in the UI is a big problem facing mobile phone automation.

4. The version is updated on the mobile phone every day, and the UI is definitely changing. This constantly adapts to the script and is definitely not the correct automation trend. Therefore, we try our best to be backward compatible when adapting to the script.

5. This requires the stability of the written code and its advantages, using Android UI, if we only follow the changes in Ui to write a case, it is very easy to write a case without the need for code-based people or even training for more than ten days.

6. If automation is not easy to promote, multiple sections will be transformed on the UI interface. Manual testing is intended to run with your automation, but the script is unstable (caused by UI changes ), it does not make manual staff feel how convenient it is.

7. Remember that every time we adapt to the smoke script and hand it over to the Black Box personnel for testing, there will always be a bunch of problems, which can be imagined, in order to make the code more perfect and robust, we add a configuration file, the encapsulated base and even base are also divided into the underlying base and the business base. Script automation personnel cannot maintain them all the time, but it is unrealistic to hand over it to people without code experience, this leads to the emergence of hard stones that cannot be automatically promoted.

8. However, manual tests for many problems cannot achieve better results, especially for automated stability tests. Many bugs occur only after several days and nights. How can they happen manually, therefore, automated testing cannot be abandoned, but cannot be widely used.

9. For the stability in automation, I felt very important. I was called for automation, but it was not difficult. I wrote native code, this aims to make it easier for those who do not understand the code to maintain. Later, I learned to submit bugs, analyze and track bugs, and use them on the cloud platform. However, this is a trivial task, it also reflects a person's ability to deal with trivial issues, and I obviously lack this, especially for reports using Excel

10. I understand the truth that the work I do must be presented to the leaders in a good situation. It is very important to make a beautiful report, even though I do not want. But I understand this truth.

 

This article is from the "AutoComplete" blog and will not be reproduced!