(Preliminary Exploration of Android Automated Testing The testing of programs used in the Android system should be a new field now. Many online materials used in this field are based on white box testing, generally based on the JUnit framework and android in the Android SDK Test and other namespaces, but there is a condition that it is necessary to use the source code of the program to provide a test access point, but this is not practical in many software enterprises. Many test engineers work in a completely black box, and can hardly touch the source code. Most white box tests are ended by developers themselves. Recall that the black box test automation under Windows used to use the framework based UI Automation automation test framework provided by Microsoft (the version is required to be above framework 3.0, that is, VS.NET2008 development environment). It is easy for those who are good at C # language to use it. I also wrote a lightweight automation framework based on UI Automation, which will be introduced in a future blog post. Can I do office work similar to UI Automation in the Android operating system? Surprisingly, Android's permission control is very clean, and data access between different programs can only be achieved through similar functions of Intent and contentprovider. That is to say, it is almost impossible for the automated program you developed to run in Android to capture elements such as controls on the AUT (Application under Test) interface running at that time (the term is quoted from UIAutomation, which is a bit stiff when translated into elements, so it is not translated), and you can't get the citation of active activity at that time (as of the end of this article, you haven't found a way to obtain this citation for the time being). No way to go? Can you walk inside the simulator and outside? Maybe.......
Preliminary Exploration of Android Automated Test.doc
Codepub Download Description.txt
..... Too many files omitted)
收藏
