Showing posts with label parallel testing. Show all posts
Showing posts with label parallel testing. Show all posts

6/10/2013

Parallel Testing in Action

At ELEKS we tried out an alternative approach to testing localized software product versions, called Parallel Testing.  

This time we tried parallel testing approach for game localization testing. It is a very simple online game, called "Cut the Rope" which is localized into English, German and French languages. The results were impressive!

The main challenges in game localization testing are: context issues and content preparation for linguistic review. Parallel testing helped to overcome the challenges. It allows to capture screen shots and video of entire game in just one round.


Anyway, see it for yourself in this short demo video:) 




by Nazariy Popov, R&D Expert, Localization

4/22/2013

Parallelism in Testing – To Be or Not To Be?


Today I would like to uncover the topic of parallel testing in context of test automation approaches: its potential benefits and possible scenarios.

So let’s dwell on the matter of test automation as we know it.  What can we call a common benefit on this regard?  The most obvious one can be referred to as “resource savings”.  How about we stop for a minute and try to define the tasks that are most frequently automated.  These can be – repetitive inputs, UI navigation, performance measuring, etc.  The next point would be the product areas which are eligible for the automation itself.  In case when one has to achieve 100% test automation coverage, he/she may claim – “It is possible to automate every bit of the program functionality!” – fine by me, but is it reasonable?  Is it worth spending hours of work to produce an automated test that will be run only once or twice, but can actually be tested manually in just a few minutes?  Don’t expect a unanimous answer, but in majority of such cases - resources spent are not worth results provided.  Another point that can be hard to overcome during the automation tests implementation is the maintenance of test cases.  This problem mostly affects products that tend to change frequently during the development process or during the product lifecycle.