Why we need test automation, but it’s not the right question

Software Development Done Right

Why We Need Test Automation, But It’s Not the Right Question

Seminar 21 april 2016Viktor Clerc, [email protected]

AgendaSetting the Sense of UrgencyTest Automation in PracticeTransforming to Test Automation

Seminar April 21st, 2016

2

So, Who Am I?Viktor Clerc

- Heads Xebia’s Test Automation team

- Traversed through all phases and activities of the softwaredelivery lifecycle

- Supported major organizations in implementing a testautomation mindset and strategy

- Happily busy redoing his house


3

Let’s get Started

4

First Principle Agile Manifesto

“Our highest priority is to satisfy thecustomer through early and continuousdelivery of valuable software”


5

Facts From Our TA SurveyHow often do you put software into production?


6

Multiple times per day 8,2%Daily 9,4%Weekly 12,9%Monthly 29,4%Quarterly 12,4%Twice a year 5,9%Yearly 4,1%At the end of every iteration/sprint 17,6%

Facts From Our TA SurveyWhen do you perform your testing activities?


7

After all software development activities have been completed (waterfall) 13,5%Requirements are translated into test cases by the test team 42,3%During the sprint, test cases are defined 25,0%Before the sprint starts; user stories are translated into acceptance criteria 13,5%Testing is automated throughout the sprint 5,8%

Facts From Our TA SurveyHow is testing organized?


8

A dedicated team of testers is assigned to specific projects 28,8%Full-time members of development teams are dedicated testers 43,9%Test tasks are accomplished by any team member, no dedicated testers 21,2%On the traditional way: at the end, once working software is delivered 6,1%

Continuous DeliveryThe three base principles


9

Base principle 1: Rigorous Automation

Base principle 2: Extreme Feedback

Base principle 3: Continuous Change

Testing is the most essential part of the software development process


10

Transformation to Test Automation

11

SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION USER ACCEPTANCE RELEASE

Test effort


Scrum Fall - Day 13 of 14

Todo In Progress In Test DoneTask 15 Task 13

Task 14Task 3Task 4Task 5Task 6Task 7Task 8Task 9Task 10Task 11Task 12

Task 1Task 2


12


13


“I directly support the definition of acceptance criteria”

Acceptance Driven Testing

Test effort


Are we done yet?Seminar April 21st, 2016

14

Common understandingWhen are we done?

AutomateAcceptance Tests

Living Documentation


15




Development = TestTest = Development

“Testing becomes a skill rather than a separate phase or role…”

Test effort


Why Developers and Testers Should Work Together


Developers are great automators!Let ”developers”, ”testers”, and ”business analysts” inspire each other to dogreat things! 16


17



“The setup and quality of the tests should be right to allow for smooth automation”


Development = TestTest = Development

Automate ALL“Testing becomes a skill rather than a separate phase or role…”

User Acceptance

Test effort

INTEGRATE REGRESSION USER ACCEPTANCE


What Does Your Pyramid Look like?


18

Wrap Up”Testing is Never Finished – It Is Only Ever Stopped”- David EvansIt’s not about automating tests, it’s about redefining how you want to test”It’s about when you’d like to know that your software is broken”


19

More information?Visit http://www.xebia.com/test-automation

Meet us- TestMasters – various Meetup groups- TestWorks Conf 2016 - http://testworksconf.com


20

[email protected]+31624509719

https://nl.linkedin.com/in/clerc@viktorclerc

Why we need test automation, but it’s not the right question

Technology