This presentation I gave at Testnet an is about the transition to continuous delivery and the agile adaption of Stater. Where visualisation is a key in the approach.
The setup of a Testing as a service, with a testing framework based on Selenium, Fitnesse, XLrelease , XLdelay and XLtestview
23. Maturity matrix
Maturity
24
LEVEL
5 Agile Cultuur Zorgen dat agile mindset onderdeel van cultuur
blijft door een levendige omgeving te creรซren.
4 Adaptief Reageren op wijzigingen door meerdere niveaus
van feedback
3 Effectief Ontwikkelen van software op een effectieve
manier
2 Evolutionair Opleveren van software eerder en meer frequent
1 Samenwerking Communicatie en samenwerking vergroten
translate
27. Testing example
The User Acceptance Test in a Day
Automation
โข Workshops to transition from manual testing to Living Documentation.
โข Use of Persona
โข External help to automate
โข Run in CI
โข Run in CD
28
28. Stater - 3 minuten demo29
Manual testing
Regression testing on the
acceptance environment
Automatische
Checks
REGRESSIE TESTEN OP
ACCEPTATIE OMGEVING
Handmatige
Testen
Operations
At the driver seat
Automation of UAT
29. Stater - 3 minuten demo30
Dev
Test
Acceptance Production
Manual
TestingAutomatic
Checks
Manual
Testing
Automatic
Checks
Manual
Testing
Automation current state
30. Succes
31
First test in the
continuous delivery
pipeline
Took us
10 weeks
Setup. more setup. more setup more, more setup, almost there, more more setup
test Lening in beheer
31. Stater - 3 minuten demo32
Automatische
Checks
Regression on Test environment
Manual
Testing
STAP 1
Flakiness
0
37. Test Automation โpraat[laatโ
Sprint 0 Sprint 1 Sprint 2 Sprint 3
Kickoff
Pilot
TA
Uitleg
Refinement + Retro
Pilot
Retro
Pilot
Refinement
Development
Review en
Fitnesse scenario
support
Sprint n
Pilot
team
TAAS
SM
Dev
Team +
business
Agile
Intake
inspanninginspanning
Regelt samen
met Agile
coach intake
TA
coach
presentatie
plan
TA
coach
Uitleg
Dev
Team /
Dev / test
Dev
Team +
Business +
initiator
Agile
coach
SM / POSM
SM /
TA
coach
SM /
TA
coach
Bouw US
+ Automatisering
scenario
TA
coach
Select
User story
Support op aanvraagTA
coach
TA
coach
Dev
Team +
Business +
TA
coach
Dev
Team
Dev
Team +
Business +
SM SM
Dev
Team +
Business +
TA
coach
TA
coach
SM SM
Refinement +
Review en
Fitnesse scenario
User story
+ Automatisering
scenario
TA adoptie
Dev
Team +
business
38. Speedโฆ
40
Deliver test environment from 1-2 weeks to 1 hour
Provisioning of servers from 1-2 days to 30 minutes
Deploying software from 1-2 weeks to 30 minutes
Integration from 2 months to 30 minutes
39. Lessons learned for Stater
41
โข Everyone training
โข Wait until someone wants to start
โข One coach
โข Community of practice with โjuniorโ
โข Bottom up approach
โข Ownership of Test automation in one team
โข If time permits the team can pick it up
โข Wait to be asked to try automation
โข Automation is not easy
โข Design patterns also apply for test code
โข โRealโ developer needed
โข Agile mindset is not easy
40. What works for Stater
42
โข Pilot teams โ3 sprintsโ
โข Open community
โข Walk in sessions
โข Training while being coached
โข Discuss guidelines
โข Sonar
โข Development skills needed
โข Place improvement on the backlog (20%)
โข Start with a picture
โข Donโt tell them how to automate, explain what automation can do for you.
โข Test automation is very useable to accelerate your manual testing
โข Business/OPS at the driver seat
โข Checks for the CD pipeline
โข Support by management
VISIBILITY
41. The challengesโฆ
โข Extending the test coverage of automated test
โข More teams using test automation.
โข More ATDD
โข Not all testers are developers.
โข Collaborative code ownership
โข OPS in the agile teams