Presentation covers: - Selling the test automation - Frameworks / Tools Reusability - Whole Team Approach Presentation from ConSelenium 2018.

1. Automation in the world of projects
A few thoughts from the business perspective
Automation in the world of projects 1
Zbyszek Moćkun,
Global Head of QA Practice @ Cognifide

2. Intro
2Zbyszek Moćkun Automation in the world of projects

3. Agenda
3
01 The world of projects
02 Selling the test automation
03 Frameworks / Tools Reusability
04 Whole Team approach
05 Summary
Zbyszek Moćkun Automation in the world of projects

4. The world of projects
▪ Project-based company
▪ Mostly Web, where the center
of the galaxy are
Content Management Systems
▪ Delivered by Adobe or Sitecore
▪ Which are Customizable
▪ And Integrated with everything
(even black hole)
4

5. Selling the test automation
Automation in the world of projects 5Zbyszek Moćkun

6. ROI
Return on Investment
6

7. Coverage
 Code Coverage
 Test Case Coverage
 Requirement Coverage
 Feature Coverage
 10%, 50%, 80%, ...?
Zbyszek Moćkun Automation in the world of projects 7

8. Does
TEST AUTOMATION
bring
BUSINESS VALUE?
8

9. Business Values
 Delivery approach
– Number of releases
– Continuous Delivery
– Should releases be production ready?
 Time to release
– SLA for defects
– Lead Time (Time to deliver new feature)
 Extendability and Maintainability
– Including costs
 Critical areas
– Technical and business
 Other issues that our client faces
Zbyszek Moćkun Automation in the world of projects 9

10. Frameworks / Tools
reusability across projects
Automation in the world of projects 10Zbyszek Moćkun

11. The advantages of reusability
 Cheaper
 Faster
 Ready and existing infrastructure
 Teams are familar with the tools
 Tools are specialized
Zbyszek Moćkun Automation in the world of projects 11

12. Client’s concerns
 Client is the owner of the code -
reuse your internal framework and
give it away
 List of approved tools / frameworks -
your internal frameworks are not in
the list
 If you use internal framework - do you
share the code with us?
 Who covers the maintenance costs?
How do you ensure us that we will
not be in the position to get rid of your
frameworks?
Zbyszek Moćkun Automation in the world of projects 12

13. IPs concerns
 How much our internal IPs are worth?
 Can we get additional money from internal
tools?
Zbyszek Moćkun Automation in the world of projects 13

14. The results
 Test Automation starts very late or at the end
of the project.
 We produce a lot of technical debt and its
elimination costs us a lot more.
Zbyszek Moćkun Automation in the world of projects 14

15. Let’s OPENSOURCE
!!!
15

16. Common benefits
 People are proud
 We (people and the company) are
recognized as experts
 Company values
– knowledge sharing
– build a community
Zbyszek Moćkun Automation in the world of projects 16

17. The unexpected reward
 Bigger project scope = more money
– We sell automation
– We train the client team
– We build the test automation infrastructure as a
part of the project
– We maintain the test automation infrastructure
too
Zbyszek Moćkun Automation in the world of projects 17

18. Automation as whole
team approach
Automation in the world of projects 18Zbyszek Moćkun

19. Zbyszek Moćkun Automation in the world of projects 19
Automation Responsibility Square - Testing Experience, June 2011

20. What has changed
 Improved quality of features delivered by devs
 Developers interested in automation
 Automation as part of application code
 DoD - Delivered and Maintainable
 Switch from Testing to Quality Assurance
 Better understanding of Test Pyramid
 Continuous Delivery
Zbyszek Moćkun Automation in the world of projects 20

21. Zbyszek Moćkun Automation in the world of projects 21
Automation Responsibility Square - Testing Experience, June 2011

22. Zbyszek Moćkun Automation in the world of projects 22
Automation Responsibility Square – April 2018

23. How it works
 QA as the owner
 Test automation training for dev at the
beginning of projects
 DoR - what we want to automate
 Two-side Dev <-> QA code reviews
 QA Demo - automation as a part of the demo
 DoD - Delivered and Maintainable
 Automation as a part of technical debt (assign
tasks for the next sprint, add labels, …)
Zbyszek Moćkun Automation in the world of projects 23

24. Summary
• Automation is not business value
• Open source open doors
• Move automation from tester to whole team
Zbyszek Moćkun Automation in the world of projects 24

25. 25
Thank you