The sample of automation strategy

1. When we can start to automate:

·         Stability of the product/application is ensured;

·         Interface to be tested has been identified;

·         Scope of automation has been defined;

·         Individual testcases to be automated have been identified;

·         The right tool has to be decided

2. What we will automate:

·         Functional testing;

·         API or Web Services

3. Managing automated tests

·         Organizing tests;

·         Organizing test results

4. Automated system for the formation and distribution of test results

5. Automated system for storing the results of automated tests - for charting retrospective detection of errors in the tests, assess the dynamics of growth / decline of quality applications that require not only the past, but previous results. Better to store them in a database

Programming language: Java

Building tool: Gradle

Java Test Framework: JUnit

CI Server: TeamCity

Development IDE: Eclipse

Source Code Control: Git

Selenium WebDriver

High level road map:

Steps	Task	Estimates, h	Priority
Environment preparation	Request at least 2 VMs on ESX server:  1 (VM1) for CI and 2nd(VM2) for Automation Testing, add extra VMs for each test configuration	16	P0
Environment preparation	Deploy CI (TeamCity) on VM1, Configure authorization, permissions,  etc.	8	P2
Environment preparation	Prepare VM2 for automation: Install WebDriver, Gradle, Eclipse, Java JDK	4	P0
Implementation	Implement 1-2 Stable Test Cases	8	P1
Implementation	Add ability to launch on another browsers	8-16	P1
Integration	Submit changes to SCM: Git	4	P1
Integration	Add Nodes for each test configuration on CI and integrate Tests with CI	16	P1
Dev build integration	Integrate dev builds with CI	8	P2
Dev build integration	Integrate dev Tests with CI and trigger them on submit	8	P2
Increase Coverage	Set some target for automation, e.g.: 30% of high priority Test Cases (TC) and increase coverage for all configurations	Number of TCs* Estimate per 1 TC	P3

Please pay attention that configuration steps (Step 0) can be executed either on local machines or on VMs, but VMs are preferable, also CI deployment can be performed in parallel and it has lower priority. 

Other tasks in backlog:

1.       Define TC management system and move from Excel to TCMS 

2.       Define code convention

3.       Refactoring