יורי סיגל

Having a Quality Assurance automation become a natural thing for many IT companies.
I will not proceed explaining all the advantages of automatic testing.

The big question for any company is how to implement an automation testing:
who will lead and develop the automation project,
what automation testing tools exist
how much such a project may cost to a company,
what automation testing frameworks exist,
whether to use an outsourcing or implement the project in house.

Here you have a case studies of our clients:

Some company decided to have an automation testing because its software had been successfully sold, but there were a lot of complains from costumers regarding bugs.
The company decided to hire an outsourcing team to develop an automation testing project. It resulted in hiring one QA Engineer who was working in company's office for 10 months. At the end of 10 months there was no result and the money was spent.

Let's see what happened:
The outsourcing company was an experienced and well known company, the QA Engineer was an experienced and educated junior computer engineer.
He entered the position with abstract knowledge of what development is and some real programming experience, but without any understanding what tools and frameworks exist in the area. He began the project from scratch: for example if there was a requirement for an HTML report, the Engineer wrote a lot of unnecessary code building HTML document with HTML tags. The solution for that requirement is pretty simple: most of existing frameworks already give an HTML report generation as part of executing test cases.

Another important thing is how to choose a test tracking tool. There is a lot of such tools: some of them are very expensive and some of them are free.
You will have to choose one of them. From my experience of working with these tools the most important thing that must be taken into consideration (no matter if this tool is free or a license has to be purchased) is to know how to use this specific tool.

Having in mind all that I have noticed above, the best and the cheapest way to begin an automation testing project is to have an experienced QA staff. This is crucial at the beginning of a project.

What we can do for you:
Start an automation testing project from scratch.
Select a QA automation framework that best fits your needs.
Deploy working environment which in turn includes a test tracking tool -- TestLink.
Create a skeleton of an automation test project with a number of a real test suites and test cases (of course it will be based on a specific SUT).
Provide a well structured test code (written in Java) - additional test cases can be easily added to a test project code.
Guarantee all components to be consistent with each other: the test tracking tool with a test project execution, automatically generated test results will appear in the test tracking tool, automatic test project building, utility scripts, that for example, will deploy a SUT to a testing environment.

Our specializations are:
Functional testing
API testing
WEB UI testing - web driver (Selenium 2)

Test environment will consist of:
A physical appliance with installed VMware vSphere Hypervisor 6.0 free license up to 32 GB RAM.
All required instances of VMs test project host VM, test tracing tool VM, VM for a SUT(s).

Selenium 2 web driver - web UI automation.