1.
1
From Manual to Automation.
QA Automation team startup.
Problems and solutions.
Shapin Anton
October 29, 2016

2.
2
• Lead Software Test Automation Engineer
• 9+ years in IT
• Areas of my competency: manual,
automation, performance and etc.
• Successfully completed 6 BDD projects.
• 1 BDD projects in progress.
Email: anton_shapin@epam.com
Skype: anton_shapin
GIT: http://github.com/kirlionik
Shapin Anton

3.
3
Agenda
Problems of migration from
Manual to Automation
1
Organization problems of QA team2
Example of test system
architecture
3
Questions4

4.
4
LET`S START !

5.
5
Problems of migration from Manual to Automation
Not a lot of projects are ready work with
Junior automation testers
1
How to increase efficiency of Junior
automation testers ?
2
Often it is not clear what Junior needs
to know.
3
Most of the automation courses are
strictly theoretical.
4

6.
6
The questions for organization of QA team:
What level should Automaton
tester have?
1
How to provide "technical" team
motivation?
2
How to increase efficiency QA
team?
3
And other important questions …4

7.
TEST SYSTEM
Team members: Junior Automation QA/Manual QA + Middle
Automation QA/Senior Automation QA = POWER
Technology:
• Java
• Maven
• Cucumber-JVM
• Java-Spring(base)
• JUnit
Architecture: Modular.
Team building preconditions

8.
8
Architecture of test system

9.
9
Structure of qa-parent: Acceptance tests
Acceptance tests
Test logic
Implementation
of Test logic
Configuration
Feature files
Step Definitions classes
Spring configuration class
Responsible: Middle Automation QA и/или Junior Automation QA or
Manual QA

10.
10
Structure of qa-parent: Qa-common-module
Qa-common-module
Services
Common Utils
Reports
Containers
Classes are responsible for:
• Work with REST/SOAP protocols
• Work with DataBase
Examples:
• Work with PDF/DOCX files
• Work with tokens
• Work with ZIP files
Examples:
• Report generation
• Create attachments
• Logger
Responsible for transfer data between steps
Responsible: Middle Automation QA, Senior Automation QA

11.
11
Structure of qa-parent: Test-config
Test-config
Env config files Properties files
Responsible: Middle Automation QA, Senior Automation QA

12.
12
How it works
qa-test-config
qa-common-module
Acceptance tests
Performance tests
Use

13.
13
Junior Automation Engineer skills improvement:
Learn HOW to write automated test
cases.
1
Study how automation tests work IN
PRACTICE.
2
Try to develop matchers of any
complexity BASED ON REAL EXAMPLES.
3
Study how “backend” of test
system works.
4

14.
14
Middle Automation Engineer skills improvement:
Study how “backend” of test system
works IN PRACTICE.
1
Study HOW TO work with different file
formats, database, REST and SOAP
services.
2
Study tests systems architectures in
details and understand pros and cons.
3
Develop the ability to learn the less
experienced professionals
4

15.
15
Senior Automation Engineer skills improvement:
Solve complex problems within the test
system.
1
Understand what exactly should be improved
in test system.
2
Analyze the applicability of new
approaches, testing tools to the current
system.
3
Improve skills of QA team
management.
4

16.
16
Pros:
Solving complex problem does not require QA
team from only high-level experts.
1
High "technical" team motivation.2
Good efficiency of Junior QA engineer.3
Flexible Team Management.4

17.
17
Restrictions:
This approach works when a team consists of 2 or
more people.
1
Cucumber is critical for some projects2
Senior QA engineer have to known base Java-
Spring
3

18.
18
Summary
1. This approach was tested on 4 projects and shown to be
effective
2. It lets solve not all problems associated with the QA team
management.
3. It simplifies and accelerates education process of less
experienced specialists
4. Manual QA engineers make a contribution to the
development of automated tests.

19.
19
Thank you for attention!
Email: anton_shapin@epam.com
Skype: anton_shapin
GIT: http://github.com/kirlionik