Q&A on Mobitaz Android Test Automation Webinar

On the fifth of June, 2014, we conducted a webinar on Mobitaz, MSys’s Android test automation tool. In this webinar, a number of professionals from various companies on testing and general quality assurance participated. Needless to say it was a big success.

It can be challenging for a quality analyst to choose the right mobile-functional-testing tool for his testing purposes. Manual testing or the use of automation tools with limited testing capabilities can be a hindrance in expediting the QA process.

Mobitaz (MSys Android test automation tool) team at MSys explored the need for a device- and an OS-agnostic mobile testing tool which can give the assurance to a QA team that testing isn’t compromised and too much time is not taken in a QA cycle. Discussions made in the Mobitaz webinar will bring a massive change in the traditional automation technique/solutions.

Some of the interesting discussions initiated by the quality assurance personnel from leading companies are as follows:

Parallel execution

Question: Does it mean that I can run a test made for Kit Kat on Gingerbread and ICS at the same time?

Answer: Yes. Concurrent playback on Kit Kat, Gingerbread and Ice Cream Sandwich can be achieved through Mobitaz.

Question: So, Mobitaz adapts to different android objects that differ between OSes? Like progress bar between Gingerbread and Kit Kat?

Answer: Yes. This is something unique about Mobitaz. The tool can record a test case once and play it back across any Android device or OS version. Mobitaz has the intelligence to recognize objects with different Android versions. Through this capability, it can make successful parallel test executions.

Advantages

Q: What are the advantages of this Android test automation tool over other mobile automation tools in the market?

A: We compare Mobitaz directly with other tools which offer a lab-based solution. A few of the advantages over other mobile testing tools are:
• Support for
o Android Custom components
o Android Web-View components
• Parallel execution
• Testing on real devices without rooting
• Detailed reporting with easy option to export and share to PDF format
• Key measurements of resources such as battery, CPU, memory etc.
• Mobile functional testing for Android versions from Gingerbread to the latest version
• Simplified licensing model
• Cost-effectiveness

Script-less Testing

Q: Does Mobitaz Android test automation tool require any scripting knowledge to create, execute, and generate reports?

A: No. Mobitaz is a script-less test automation tool and does not require any programming knowledge for functional testing of mobile apps. Mobitaz has intelligence to manage test cases, through features such as Object Repo, Test Case Editor, Reports, etc.

One thought on “Q&A on Mobitaz Android Test Automation Webinar”

  1. Nowadays everyone looks for cool utilities and features for their customers. Few trends to keep an eye are mentioned below.

    As ‘objects’ get “smartified”, deep challenges to social conventions will emerge. Is Mobitaz already able to test such needs in the market and if not, do you have plans in improvising it for the enterprises to get going in developing such applications.

    Features that are now aggressively been/going to be available in Android too like –

    ShinobiControls charts and its various controls what you may find people call it as “Bitesize Android KitKat”.

    Transitions –
    Unique methods of transitioning from one layer or section of the interface to the next. It needs to be smooth, but not feel sluggish. It’s a fine balance between the two, even more so when you take into account the desire to stand out amongst the crowd, but such restraints continue to push innovation and creativity.
    i) CSS3 Transitions
    Transitions without CSS3 Transitions

    ii) Theming of an app
    Color as facet of an app to make a feel to the user as per the study on psychology behind color

    iii) Layers/Depth within apps
    Adding of various possible parallax adding to the ongoing designing and development of interfaces

    Blur to add to effectiveness of the UI of an app
    Importance in the details
    Content Impermanence
    Better Use of Sensors
    Experimentation with Navigation System
    Single-use Pages
    Browser’s Integration with Oses
    Physical Products Coinciding with Apps
    Skeuomorphism for Mobile Interface Design – Encouraging Realism

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>