Cultural change of testing

9
Brijesh Prabhakar 2 December 2015, Bangalore Testing as a Cultural Change in the Brave New World of DevOps 1

Transcript of Cultural change of testing

Page 1: Cultural change of testing

Brijesh Prabhakar 2 December 2015, Bangalore

Testing as a Cultural Change

in the Brave New World of DevOps

1

Page 2: Cultural change of testing

What is Brave about the New World

“By 2016, 40% of App Dev organizations will have joint initiatives with

operations in support of continuous delivery and simplified release

management.” — Gartner 2

Source: Forrester on DevOps, 2014

Page 3: Cultural change of testing

DevOps – (New) Ways of working

Make Agile Iterative way of working based on business

priorities and continuous improvement

Collaborate Empowered, Cross Functional, stable and

knowledgeable teams

Automate Automation of manual tasks

(Build, Deploy, Test, Release & Monitor)

Simplify & Standardize

Integrated solution stack and use of standardized proven services & tools

Traditional “Audit” based testing approaches will not work in the future

3

Page 4: Cultural change of testing

A Tester’s mindset in a DevOps World

User Empathy

Technology Savvy

Testing Skills

• Develop end user perspective

• Cultural understanding

• Domain / Functional Expertise

• Beyond application features / UI

• Understand underlying platform

• Understand errors

• BDD, Service Virtualization, Triage

• Ability to automate tests

• Preserve application value 4

Page 5: Cultural change of testing

Challenges in Automation

Source: WQR 2015

• Automation is at the heart of Agile (and DevOps) methodologies

• Level of automation is an indication of maturity of testing processes used

• Levels of Automation is increasing and often going beyond Functional Automation

In spite of these challenges…

5

Page 6: Cultural change of testing

Traditional Test Automation (& why it fails)

• Late start of automation activities in the lifecycle

• Low utilization of automated scripts resulting in low RoI

• Progress measured by number of scripts rather than application coverage 6

Page 7: Cultural change of testing

Future of Automated Testing

Regression Focused

Focused on existing, working functions; ROI and repetitive tests

Progressive Feature Tests

Enabled by TDD & BDD frameworks and increasingly mature tools

Beyond UI Functions

Batch Jobs, Services, ETL jobs, Test Data Management, Service Virtualization

Code Quality Reviews

Integrate Automated Code Quality as part of Sanity Tests for new builds

Today

7

Future

Page 8: Cultural change of testing

Automation is not just a testing initiative…

8

• Cost of Testing

• Faster Time to Market

• BDD driven approach

• Less loss in translation

• Early detection of bugs

• Test for code quality

• Increased test coverage

• Efficiency gains

Page 9: Cultural change of testing

9

Brijesh Prabhakar Director and, Head of Testing, India GDC, Atos [email protected]