Mobile devices are everywhere today and enterprises already understand that keeping one step ahead of the mobile game is essential. Chances are, that if they have not already, enterprises will be investing in mobile applications in the near future.
With this development, comes the need to ensure that creation of enterprise mobile applications is done in the best, most secure way possible. Despite the fact that there are a large number of requirements needed in an average testing tool, the following is a concise list of less-than-obvious recommendations that will ensure that you choose an excellent mobile testing tool.
One Object Repository for all Mobile Platforms
A mobile application testing tool that can run a single test on any device being tested has an obvious advantage over a mobile testing tool that requires modifying the script for each new device. The way to achieve this is through object reuse via an object repository which identifies runtime objects based on characteristics specified by the testing team. In other words, object descriptions are stored in the object repository and when each test is run, the Object Repository window provides information about the test object such as its type, where it is stored and other details for each mobile platform.
Advantages of Object Repositories;
• Test maintainability- no need to edit all scripts in the event of a button label change
• Test portability- a unified Object Repository leads to the ability to use the same script on different platforms without any modifications of the script
• Simplification of test scripts through separation of physical attributes and test scripts
• Improved script readability as objects are referred to using object names
With this development, comes the need to ensure that creation of enterprise mobile applications is done in the best, most secure way possible. Despite the fact that there are a large number of requirements needed in an average testing tool, the following is a concise list of less-than-obvious recommendations that will ensure that you choose an excellent mobile testing tool.
One Object Repository for all Mobile Platforms
A mobile application testing tool that can run a single test on any device being tested has an obvious advantage over a mobile testing tool that requires modifying the script for each new device. The way to achieve this is through object reuse via an object repository which identifies runtime objects based on characteristics specified by the testing team. In other words, object descriptions are stored in the object repository and when each test is run, the Object Repository window provides information about the test object such as its type, where it is stored and other details for each mobile platform.
Advantages of Object Repositories;
• Test maintainability- no need to edit all scripts in the event of a button label change
• Test portability- a unified Object Repository leads to the ability to use the same script on different platforms without any modifications of the script
• Simplification of test scripts through separation of physical attributes and test scripts
• Improved script readability as objects are referred to using object names
Complex Identification of Native, Web & Hybrid Apps
When a mobile application development team wishes to test a native, web or hybrid application, there are different identification techniques available. A complex identification technique is much more advisable due to the ability to zoom in on details in a much more sophisticated manner than an elementary identification technique, thus leading to much more precise and reliable identification. When a more simplistic tool is used, the best possible scenario is that bugs remain unidentified, the worst possible scenario is that the wrong object is identified and there is no way of knowing where the bug is…
A complex hierarchy (tree-based) identification method reveals the hierarchy behind the objects that are clicked on and not just the object’s properties.
A complex hierarchy (tree-based) identification method reveals the hierarchy behind the objects that are clicked on and not just the object’s properties.
Enterprises wanting to develop mobile applications should therefore make sure that the tool they purchase in order to test their applications is capable of complex hierarchy identification to save the money, time and effort of the QA team.
In addition, making sure that the mobile testing tool that your enterprise chooses can integrate into CI environments means that you end up taking preventative (and not corrective) measures.
The following illustation presents how complex identification techniques work- in order to identify the required object (in this case the little box found to the right of the text “Help”), the “parent” object (container) is found (in this case “LineartLayout”, followed by a “son” of the “parent” (in this case the “Help” text).
In addition, making sure that the mobile testing tool that your enterprise chooses can integrate into CI environments means that you end up taking preventative (and not corrective) measures.
The following illustation presents how complex identification techniques work- in order to identify the required object (in this case the little box found to the right of the text “Help”), the “parent” object (container) is found (in this case “LineartLayout”, followed by a “son” of the “parent” (in this case the “Help” text).
“On the Fly” iOS Instrumentation
When developing mobile applications, instrumentation of the application is a critical step. Instrumentation is the act of bringing to the surface the properties of an element- such as its ID-and its hierarchical placement. It is possible for the QA team to carry out instrumentation after the application has been worked on by the R&D team, and indeed this is the most common scenario. However, the ability to carry out instrumentation “on the fly” means that it is possible to entirely skip over the stage of the R&D team, allowing the QA team to carry out instrumentation directly, with no need to understand or change the code, thereby saving valuable time.
When developing mobile applications, instrumentation of the application is a critical step. Instrumentation is the act of bringing to the surface the properties of an element- such as its ID-and its hierarchical placement. It is possible for the QA team to carry out instrumentation after the application has been worked on by the R&D team, and indeed this is the most common scenario. However, the ability to carry out instrumentation “on the fly” means that it is possible to entirely skip over the stage of the R&D team, allowing the QA team to carry out instrumentation directly, with no need to understand or change the code, thereby saving valuable time.
No comments:
Post a Comment