![]() ![]() One is to use accessibility id which can be used the same way in both Android and iOS. Regarding issue 1 above there are a couple of ways to solve this. Because of this it is easier to maintain since only the code in the page-object class need to be updated if the UI changes while the tests that uses that page-object stay intact. This has the advantage that there is a clean separation between the test code and the page specific code such as locators. This is in general a good design pattern for your tests where you create object-oriented classes that correspond to the specific pages in the application under test. One general solution, not only related to the issues above, is to use page objects. You can easily share code and content between your tests on the different platforms.Īnd for the issues above there are solutions. You can use one single programming language for your tests. You have one single development tool (IDE) for your test development. No Appium still solve a lot of the main issues. So does this mean that Appium is not a good solution? a setting is maybe done using a drop-down list in Android while using a slider in iOS. Or some steps could maybe differ a bit between the platforms, e.g. need to perform some extra steps in one platform compared to the other. So to achieve a specific test scenario you may e.g. In both platforms you can use xpath and classname but they will never be the same in both platforms.Įven though the apps for the different platforms are built to look and behave the same way there are platform specific implementation and design guidelines which could lead to small differences in behavior between the platforms. in Android you can find elements by resource id which is not supported in iOS. In most cases you will not be able to find an element using the same identifier in Android and iOS.Į.g. In theory you could create a test that works on both platforms but in practice it is not that easy and it is basically because of two issues. So is it really that easy that you just write one testcase and then it magically works on both platforms? This enables code reuse between iOS and Android testsuites. They are also written in different languages and with different development tools (IDEs) so even if the applications work the same it is hard to share any code between the tests for the different platforms.īut this is where Appium comes in. From Appiums own website:Īppium is “cross-platform”: it allows you to write tests against multiple platforms (iOS, Android), using the same API. So you then have to create and maintain two separate test suites, one for Android and one for iOS. Both Android and iOS have a couple of different test frameworks that work well but have nothing to do with each other. In most cases they look and behave the same way (except for the platform specific behavior and UI differences).Īs a test developer it is quite hard to create a good automatic test suite that works on both platforms. I have been working in a couple of projects where we have created the “same” application in both Android and iOS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |