Shift left and shift right - the testing swing - Laurent Py [email protected] @py_laurent blog.hiptest.net
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Shift left and shift right: the testing swing
Shift left and shift right- the testing swing -Laurent [email protected]@py_laurentblog.hiptest.net
1
From waterfall (2003)Product: Test Designer, eclipse plug-in in JAVA
Waterfall process
1 release every 6 months
Few tests and no TDD
1 month (x5 people) to do release testing before deployment
2
to DevOpsProduct: Hiptest, BDD in the cloud
Mix of Scrum&Kanban process
We do BDD
Multiple deployments a day
Acceptance tests are part of the CI process
3
Break silos
4
Its all about speed of feedback loop
5
Its about speed of feedback loopI like what I've seen so far and I've been very impressed with the live support. Your team managed to identify and fix a bug I'd found within about 12 hours.Tom GrahamProduct Innovation Software Manager
6
How to ensure quality of deliverables?
7
8
Why? Is it worth doing it?
9
Put value before correctnessWhy? Is it worth doing it?
How to ensure quality of deliverables?
10
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
11
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
12
Behavior driven development:Create shared understanding based on examplesUsing a common business terminologyDefine the stop Live specification & documentation when automated
What should we build?1
13
What should we build?1
14
What should we build?1
15
Challenge business assumptions Why should we build it?1
16
As a Product OwnerI want to link a Hiptest scenario with a Jira issueSo that I can get traceability between tests, user stories and issues
Why should we build it?1+
17
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
18
/ Is it really worth it?2
19
Is it really worth it?2
20
Is it really worth it?2
21
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
22
How to automate?3
CI
23
Refactor3
Martin Fowler
24
Evil of duplication3
25
Evil of duplication3
26
Key success factors3RefactoringCI+
27
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
28
Is it reliable and does it scale?4
29
The testing matrix we use todayBuildProductionNew Feature/ experimentWhat should we build and why?Is it really worth it? Validated featureHow to automate?Is it really reliable and does it scale?
30
The tools we use today
31
To the test managers
32
ABIGTHANKSLaurent [email protected]@py_laurentblog.hiptest.net
33
Related Documents
