Automated Testing Service Group
Automated Testing Service Group offers a complete range of testing automation services:
- testing scenarios development
- automation tools selection
- testing scripts development
- regression and functional testing
- employee training
Our main objective is to improve software quality.
Intelligent approach to automation enables us to considerably reduce the time required for testing as well as for testing scripts development.
Latest in blog
Cucumber is just another Ruby-based test engine which gives the ability to write human language automated tests. But this is only one particular aspect. But there\'s another aspect. Cucumber is just another one auxilary utility as many others. As many others Ruby-based solutions the Cucumber can be integrated into some infrastructure. In particular there\'s ability to define some specific tasks to be done. In addition to this sometimes it\'s necessary to check if overall solution is built without any errors, get the list of the tests marked with some specific tag or list the steps which do not have step definitions implemented or so. All this stuff is quite useful for tests development.
Very often test automation solution becomes so complex that test development require quite strong programming skills. At the same time most of the solutions has a trend to simplify test automation. This can be achieved by various wizards, approaches introduction and devekopment of engines implementing these approaches. In particular,there\'s quite popular approach named keyword-driven testing where tests are actually tthe sequence of keywords structured in tabular form. But there\'s more quirky approach when test instructions are written using "natural" language with corresponding programming implementation. For instance, there\'s engine named Cucumber for Ruby.
Of course XPath locator is one of the most quirky and one of the most precise locator. But this universality is accompanied by the main disadvantage of such locator types. It is slowness. This disadvantage is clearly seen while running the tests under IE while Firefox works with xpath pretty well. This problem is related to internal browser features in particular to the libraries being used for elements location definition. But this is another story. The main thing is that tests which intensively use XPath work extremely slow under IE and this feature is the cause of huge variety of problems related to execution speed as well as quality of the tests itself especially during operations with dynamic content. For this reason CSS locators can be good alternative of XPath. What can we do with CSS locators?
PushButton is one of the simplest controls, but there could be problems even with it. In this blog post we will show several ways of how to perform a non-standard Click() action when standard Click can not be used.
GUI level automated testing has a lot of surprizes related to interaction with window objects. The main problem is that each automation tool has its own set of the most effective solutions to the problem of window definitions maintainability. But these are the most effective solutions for each particular case ( not in general ). Nevertheless, there are some mechanisms which are common to a wide range of tools. Or at least there are analogs. For example there is such approach as windows definitions mapping which provides the ability to set some alias into correspondence to actual window definition. Such solution implementation in TestComplete has one key disadvantage: in case of windows hierarchy modifications for some particular object there is necessity to re-map all child objects. The alternative to mapping was introduced in TestComplete version 6. There was an Alias functionality providing the ability to construct mapped objects hierarchy. But this solution has another disadvantage: slow performance. So, we need some mechanisms allowing to minimize time costs for window definitions modification in case of UI changes. Let's examine this problem on some particular case.