Archive

Posts Tagged ‘testing’

Successful UI testing of mobile applications on real devices and emulators with RoutineBot

May 12th, 2010

Any test engineer even without programming skills can easily create complex test scripts using RoutineBot

Ilya Gorshkov, Software test engineer,

MERA NN, Nizhniy Novgorod, Russian Federation

We use RoutineBot as a test automation toolkit for about 1 month. We’ve already tried a lot of tools around the world. We’ve chosen RoutineBot because only using this tool we can create flexible and  reliable automation scripts and do it really fast.

We do UI testing of various mobile applications on both real devices and emulators. Using RoutineBot automation of emulator testing is no longer a problem for us.

Another good advantage of RoutineBot usage is that probably any test engineer even without programming skills can easily create complex test scripts using RoutineBot.

Also I want to thank RoutineBot team for outstanding support and want to say that our test team is looking forward to extend our partnership and involve more projects in test automation.

  • Share/Bookmark

admin Testimonials , ,

Checklist for GUI testing – making GUI testing more bullet proof

February 28th, 2009

Bullet proof GUI test is a test script which will run perfect in 99% of cases, without any help from your side.  I assume that you already have some test plan and know what you need to test and now you are working on the script level to incorporate in the script all your ideas. So here is a check list to follow.

Prepare Environment

  • Turn off any application on you PC that might show some unexpected messages, windows or somethings else. Turn off Skype and ICQ – anything that can appear on the screen without your control.
  • Before processing with any GUI related things, e.g. clicks and mouse moves, make sure the application that you are going to test automatically is opened. In RoutineBot you can use one or more MouseFocuse functions, which will return 1 if some image marker was found and application is ready to be tested.

Running test – debug on fly

  • Add some debug messages in your script, e.g. show some hint near the system clock or write some log to the file. In this way, it will be easier to find possible problems in future.
  • Make sure you are writing results of test in some text format. In this way you will be able to pass results of test to some other application or print them out in the command line screen. RoutineBot can write internal variables to the output files.

Control testing results

  • After the test or some automation process there is some chance that testing or automation was done wrong because of some unknown reasons. So, it is good idea to make a screenshot of some resulted window, so after the test you will be able to manually control results. With RoutineBot you can make screenshots.

Learn more about commands supported in RoutineBot.

  • Share/Bookmark

admin Articles , , , ,