В рамках доклада мы поделимся примерами проектов, на которых есть автоматизация, но нет ни одного специально выделенного инженера для выполнения задач, связанных с автоматизацией тестирования. Затронем такие вопросы как: что нас привело к такому решению (отказаться от test automation инженеров); сложности, с которыми мы столкнулись; бонусы, которые мы в итоге получили.

1. Test Automation without Test
Automation Engineers
Maria Teryokhina, Vladislav Kuznetsov,
2020

2. Agenda
2
1. Introduction: History of the Decision
2. Idea Forming
3. Obstacles and Solutions
4. Implementation Examples
5. Our Practices
6. Disadvantages and Advantages

3. About Us
• Maria Teryokhina
• Education:
• 2010 – master’s degree
• Work Experience:
• Test Engineer since 2008
• Test Lead since 2012
• Process Advisor since 2019
• Vladislav Kuznetsov
• Education:
2018 – master’s degree
• Work Experience:
• Support Specialist in 2014
• Front End Developer since 2015
• Tech Lead since 2019
3

4. About Company
4

5. 2015
Test Automation “Expert”
OR
Developer “Trainee”?

6. History of the Decision
6
~ 30%
Evaluation/Reporting
Tasks
Environment Preparation
Estimation
Planning (Strategy)

7. Idea!
7

8. Testing Theory
Functional Tests (GUI)
Integration Tests
• Developers
Component Tests
• Developers
Unit Tests
• Developers
8

9. Obstacles &
Solutions
• Test Automation Strategy + Tactic
• Responsibilities
• Technical Skills and Knowledge
• Test Frameworks & Tools Knowledge
• “Developers don’t Like to Test” ©
• Customer Satisfaction
9

10. Project #1
1
• Setup: Selenium + Cucumber
Authors: business analytics
Source: JIRA
TE role: providing reports
Reports: weekly

11. Examples
11

12. Project #2
2
• Setup: Protractor + Appium
Authors: business analyst
test engineers
Source: JIRA
TE role: checking reports
Reports: by request

13. Examples
13

14. Project #3
3
• Setup: Cypress + Cucumber
Authors: all team members
Source: Git repository
TE role: design check list
Reports: nightly

15. Examples
15

16. Disadvantages
• Test Scenarios Description
• Developer’s Effort
• Developer’s Supporting
• Performance Scaling
• Test Automation Priority
• “Developers Don’t Like to Test” ©
16

17. Emergn BDD
Best practices
• Finish Story – Finish Gherkins
• Make Universal Scenarios
• Test Scenarios, not UI
• Test Success Flow
• Priorities for Gherkins
• One Dictionary for Team
• Repository for Gherkins, JIRA for Description
17

18. Results
18
• Volume
• Questions
• Time Effort
• “Developers don’t like to test” ©
Sprints~5

19. Results
19
Sprints~5

20. Advantages
• Code Testability
• Team Joining
• Shared Responsibilities and Expertise
• Product
• Technical
• Developers Know the Product Better
• Developers Involved to Requirements Analysis and Testing
• Everyone Doing their Jobs!
20

21. Conclusions
21

22. Thank you
Skype:Skype: mariateryokhina