08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
Why we need test automation, but it’s not the right question
1. Software Development Done Right
Why We Need Test
Automation, But It’s
Not the Right Question
Seminar 21 april 2016
Viktor Clerc, vclerc@xebia.com
2. Agenda
Setting the Sense of Urgency
Test Automation in Practice
Transforming to Test Automation
Seminar April 21st, 2016
2
3. So, Who Am I?
Viktor Clerc
- Heads Xebia’s Test Automation
team
- Traversed through all phases
and activities of the software
delivery lifecycle
- Supported major organizations
in implementing a test
automation mindset and strategy
- Happily busy redoing his house
Seminar April 21st, 2016
3
5. First Principle Agile
Manifesto
“Our highest priority is to satisfy the
customer through early and continuous
delivery of valuable software”
Seminar April 21st, 2016
5
6. Facts From Our TA Survey
How often do you put software into production?
Seminar April 21st, 2016
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%
7. Facts From Our TA Survey
When do you perform your testing activities?
Seminar April 21st, 2016
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%
8. Facts From Our TA Survey
How is testing organized?
Seminar April 21st, 2016
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%
9. Continuous Delivery
The three base principles
Seminar April 21st, 2016
9
Base principle 1: Rigorous Automation
Base principle 2: Extreme Feedback
Base principle 3: Continuous Change
10. Testing is the most essential
part of the software
development process
Seminar April 21st, 2016
10
11. Transformation to Test Automation
11
SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION
USER
ACCEPTANCE
RELEASE
Test effort
Seminar April 21st, 2016
12. Scrum Fall - Day 13 of 14
Todo In Progress In Test Done
Task 15 Task 13
Task 14
Task 3
Task 4
Task 5
Task 6
Task 7
Task 8
Task 9
Task 10
Task 11
Task 12
Task 1
Task 2
Seminar April 21st, 2016
12
13. Transformation to Test Automation
13
SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION
USER
ACCEPTANCE
RELEASE
“I directly support the
definition of acceptance
criteria”
Acceptance
Driven Testing
Test effort
Seminar April 21st, 2016
14. Are we done yet?
Seminar April 21st, 2016
14
Common understanding
When are we done?
Automate
Acceptance Tests
Living Documentation
15. Transformation to Test Automation
15
SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION
USER
ACCEPTANCE
RELEASE
“I directly support the
definition of acceptance
criteria”
Acceptance
Driven Testing
Development = Test
Test = Development
“Testing becomes a skill
rather than a separate
phase or role…”
Test effort
Seminar April 21st, 2016
16. Why Developers and Testers
Should Work Together
Seminar April 21st, 2016
Developers are great automators!
Let ”developers”, ”testers”, and ”business
analysts” inspire each other to do
great things! 16
17. Transformation to Test Automation
17
SPECIFY DESIGN BUILD TEST INTEGRATE REGRESSION
USER
ACCEPTANCE
RELEASE
“I directly support the
definition of acceptance
criteria”
“The setup and quality of
the tests should be right
to allow for smooth
automation”
Acceptance
Driven Testing
Development = Test
Test = Development
Automate ALL
“Testing becomes a skill
rather than a separate
phase or role…”
User Acceptance
Test effort
INTEGRATE REGRESSION
USER
ACCEPTANCE
Seminar April 21st, 2016
18. What Does Your Pyramid Look like?
Seminar April 21st, 2016
18
19. Wrap Up
”Testing is Never Finished – It Is Only Ever
Stopped”
- David Evans
It’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”
Seminar April 21st, 2016
19