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
One of the most frequently asked questions about software testing automation is "where should I start learnig an automation tool?". In this blog post we will try to give an answer to this question without using a concrete tool.
One of the most serious problem of automated tests ( especially GUI level tests ) is synchronization between test execution and application under test work. In other words, all actions being performed by the automated test have to be executed exactly at the moment when application under test is on the correct state allowing to perform required actions. Otherwise we are at risk to come across the situation when test tries to click on some object, enter some text while the form to perform these operations on is simply not available. As the result, our test goes by its fixed steps but the results and system behavior is unpredictable. And if at the same time there are no recovery scenarios the whole test set execution may be failed at once.
Every so often during tests automation we may encounter steps description like "Repeat steps 1-12" or even more interesting like instructions to repeat all steps using some specific settings. It means that we have to duplicate some code during automated tests development. But excessive code duplication may cause a number of maintainance problems. Any changes have to be made in all repetitive code occurences. And this makes additional time loss. It can be avoided in the following ways:
From time to time while reading different publications we may find the opinion that any "heavy-weight big vendor" automated testing tool ( actual tool names are usually omitted ) is associated with such thing as unmaintainable tests. But at the same moment any hand-made solution or even simple library is positioned as something flexible and easy adaptable. Of course, I also prefer taking something little and simple and using it effectively rather than taking something heavy-weight and thinking hard about how to bind it to my processes.
During development of automated tests as well as any other program components we have to make our code satisfy the following characteristics:
- Readability
- Extensibility
- Transportability
- Optimality
- Correspondence to requirements
- Maintenability
- Others ( some project-specific features )