Upload
derk-jan-de-grood
View
282
Download
1
Embed Size (px)
Citation preview
EuroSTAR webinar
Creating Agile Test Strategies for Larger EnterprisesDerk-Jan de Grood/ Valori
February 20171
Questions this webinar addresses
2
What should it address in order to
add valueIs there a need for
Agile Test
strategiesWho owns the agile test strategy
3
Testing is declining
Business[Agility]
4
Testing is on the rebound
5
Testing is embedded in development and quality is crucial, team exceeding and not trivial
Testing and business agility
Effective testing ensures that the organization can extend and change software products whilst retaining confidence in the quality and correct operation of what is delivered
[ING orange book on testing and Quality]
6
[http://www.slideshare.net/janetgregoryca]7
Some statements from Janet’s talk
Agile wants small co-located teams, but in large organizations this is not always possible. Culture: A blame culture kills innovationTesting is a team problem, but in large organization there are a lot people outside the team (Note the keynote by Diane Larsen- the Boundary Interaction map) In large projects, many projects are concurrently active and not seldom people are managed as resources (iso humans)Typical testing issues in larger enterprises are: Throwing over the wall, not knowing who to ask, integration, testers that are working in more than one team, Failing to look at release total.
8
9
Gojko Adzic on ATD 2016
10
Development Testing
e2e testing
Approval testing
Testing after deployment
Unit testing becomes less
important
Code as a service
Deploy to multiple Environments
Services over Apps
Click !
Testing is VITAL, But we
need to organize it in a way
that it clearly adds value
11
12
Needs !
Case 1: Focus on acceptance
13
14
It ain’t done until its accepted
15
Witness report: 2 outcomes
Advice to accept solution• Professional testing• Good process• Good test results
Advice to not accept solution• No professional testing• No Good process• No good test results
16
Witness proces
17
Introduce Agile
techniques
Case 2: the need for status info
18
19
It ain’t done until it’s tested
20
Testing a Central Topic Has the train arrived at the station?
Case 3: It ain’t done until it’s integrated
21
Multi team setting
22
Architecture• What are the
business processes?
• What are the components?
• What are the interfaces?
Acceptance criteria• What is the
Minimal Viable Product?
• What integrations are needed to make it work?
Requirements traceability• When are we
complete?• How do test
results add up to acceptance?
23
Missing
What should a car minimally do?
24
Planned Integration Tests
25
Integration tests
Release Date
Ensuring Integration (rough sketch)
26
Organization
Component
System
Service
Continuously(in the sprint)
Occasionally(e.g. prior to a release)
CI/C
D
MBT
Service
Virtualization
Stubbing
e2e
ST
Test
Automation
UT
Integration
sprint
Manual RT
Interface
testing
Annotation: Increasing the system (e.g from Units tot Systems) results in less frequent integration, because it becomes harder to test the integration. This has impact on the time-to-market.
Click !
27
We need to organize
something
Who will own
quality
Agile Test Strategy
28
What needs to be tested?
Feedback, steering and progress
Auditing the test work
Coaching the testing team members
Organizing tests that do not fit the sprint
29
What needs to be tested
25
Goal
Succes factors
Challenges
Unc
erta
intie
s
Worries
Fears
Does it work as a
whole?
Hygienic
tests done?
Should I accept?
Acceptance driven Test Report
30
Lot 1
Lot 3
Lot 5
Lot 4
Lot 6
Lot 2
Test reporting
31
Lot 1
Lot 3
Lot 5
Lot 4
Lot 6
Lot 2
Tell the testing story
• Do you know what is tested in the various teams?
• Do you know how well they did it?
• Do you have proof?• How do you rate the quality?• What concerns do you have
(combine the bugs and translate to business impact)?
Janet’s test matrix32
Testing is a team responsibility33
Do you know how well they did it?
Levels of strategy
Policy
Strategic
Operational
34
What could be in an operational test strategy?
EnvironmentsToolsRisk analysisOrganisition and rolesHow you use CI/CDInterpretation of (A)TDDRelation between through away & regression testsHow to do test automationFinding procedureManagement processesEtc…
35
Test Driven Development (TDD)
36
1. Business is actively involved with
defining acceptance criteria, Examples
and Scenarios
2. Development process is adopted
to fit TDD
3. Release and deployment cycles
are established
4. Backlog of (automated)
regression tests is minimal
5. Teams have sufficient test, tool
and automation knowledge
6. Tools are configured and
running on controlled environment
7. It is defined what tests need to be run at what level in the
pyramid
8. Management commits to solution and stimulates the
team to fail forward
CI/CD requisites
37
Teams Collaborate Integration is Continue
Tests are Automated
Deployment is hands-off process
No Automation Backlog
Clear Acceptance Criteria
Feedback loop to improve Testing
Frequent Product Launch
Who owns the Quality?
44
45
A job for the• Test manager• Quality master • For you?
WRAP-UP
46
Derk-Jan
ValoriColtbaan 4a3439 NG NIEUWEGEINThe Netherlands
• [email protected]• +31(0)651807878• www.valori.nl• @DerkJanDeGrood• http://djdegrood.wordpress.com
Derk-Jan
47
SuccessWith your strategy !