Test Studio - Looks promising for mobile web testing - My Review

While I was reading about mobile web testing tools, I recently came across a tool called "Test Studio". I was curious about how it works and started my usual exploration :-). The results were pretty good and tried out different scenarios and played around with the tool. It is available free for iOS and Android devices, but since I am an iPhone user, I evaluated this tool using my phone.So here goes my Analysis and Review...

TEST STUDIO - Analysis

  • Is available both for iOS and Android.

  • Free version is available which has all the basic functionalities needed to do mobile web and native application automated testing

  • This analysis is for mobile web automation capabilities of this tool

My Test Environment

iPhone 4 - OS version 5.1.1

Test Scenario

I did not want to complicate things, so tried lot of simple scenarios. I will list down some of them and skim through the various features with screenshots

Scenario 1- Installation

Easy Installation. It is as simple as just downloading the app from the App Store just like you download any other iOS application.

Scenario 2- Usability

Easy to Use.  The app is very easy to navigate and is self- explanatory in terms of letting the user know the different options available.

Scenario 3- Automation

Now coming to our big concern!!!!! How easy is it to automate using this tool??  To precisely answer this question, I played around with different options of the tool. I will list a simple automation scenario I tried and how the tool responded.My automation scenario - 

  • Type in www.google.com in the browser

  • Type in the search term "rajsubra testing" in the search bar of google.

  • Open my website www.rajsubra.com

photo

photo

Very simple scenario right :-). Now, I will go through each and every screen I had to go through to automate the above scenario.        This is the first screen which shows up when you open up the application. It gives the option of recording a test, doing a web or native application testing and the usual stuff. My area of interest is "Mobile web testing: (as you may have guessed from the other blog posts :-)) and so clicked on "Web Testing".

photo

photo

photo

photo

 Once I clicked on Web Testing, I get the above screens, firstly an option to choose "Web Application" and once I selected this, I get a screen to give a name for my Project. Once I click on the "Create" button (which you can seen in the 2nd screenshot above), the tool starts recording.

photo

photo

photo

photo

photo

photo

The above screenshots shows the various screens one by one, which came up during my recording process. In the order in which they appear above,

  • I first type in "www.google.com"

  • Type in "rajsubra testing" on the google search bar

  • Then click on my website.

Then I clicked on the bottom right most icon next to the "+" icon to stop recording

photo

photo

photo

photo

photo

photo

photo

photo

       After which I saw the above screen which gave me object level description of the various things captured during the recording process. This for me, was very similar to say recording an automated script using QTP and seeing the objects captured. I found this very interesting. Interesting why!!!!! you may ask??Interesting!!!! because, I used this screen to manipulate the data and it gives me freedom to do so. For example - I had a scenario where I entered into a website using my username and password. But, after recording, I wantedly went and gave a wrong password in the above screen and re-ran the test. It failed as expected. This helps me to do validation testing rather than just doing happy path testing :-)  I am happy that a free tool offers this functionality!!!!!!!        So just like any other automation tool, our project gets saved like the one showed above. This helps to re-run the tests anytime you want.        When you click on a recorded project you will see a screen like the one shown above giving details about the recorded scripts and the objects recorded. This is like showing a detailed test result.        Remember!!!! I was just talking about manipulating a recorded tests and re-running it. So, just as expected the test failed when I manipulated the "Google" test (The test scenario I have been describing all the while in case you forgot :-)). We can see if from the screenshot above.

SUMMARY

Overall!!!! I found that, this tool had good potential.  For getting all the standard features needed for automation in the free version, this is definitely something to look into and can be added as a complimentary test to what we already use for mobile web testing. Again, just like all other tools we have the factors like Maintainability, Reliability etc which has to be taken into consideration.I like it :-).Hit me up with any questions.

Previous
Previous

User Acceptance testing - Highly misunderstood testing jargon/phase!!!!

Next
Next

The 5 Step Process for Mobile Testing by Pairing