Talk at the TestBustersNight at 9th september 2021

1. Exploratory Testing and DevOps -
best friends?
> Te stBuste rsNight , 9th se pte mber 20 21
Sven Schirmer
Gilda Karimzadeh

2. > A G E N D A
OUR TOPICS FOR YOU
1. Who are we?
2. What do we understand as „DevOps“?
3. Exploratory Testing vs. Testautomation
4. Boost your Testautomation
5. Project example: Session based testing
6. Project example: Exploratory testing
7. Open Discussion

3. > W h o a r e w e ?
Two out of a team from
more then 650 people
We bring people and organizations
ahead - with IT.
OUR FIVE PRINCIPLES
1. We put people first – in the project and as
users, as creators and as affected persons.
2. We combine software engineering specialists
from different disciplines
to custom-fit teams.
3. We use methods and technologies in a
targeted and well-measured manner.
4. We invest in R&D. And in learning. That way
we stay ahead of the game.
5. We know our limits and cooperate with
excellent partners.
Sven Schirmer
Head of QA,
Quality Enthusiast
Gilda Karimzadeh
Test Engineer
WE‘RE HIRING
Just have a look to our website

4. > W h a t d o w e u n d e r s t a n d a s „ D e v O p s “
„DevOps is a culture, not only a framework
how software is implemented. “
In our projects, we often experience that people talk about DevOps only with the focus of pipelines and faster integration or deployment.

5. TESTAUTOMATION IS A MUST
When you want to deliver a piece of software in a fast,
regular way you must implement a valuable
testautomation that is build, maintained and used by
the whole team.
SOFTWARE CAN’T ONLY BE TESTED BY CODE
We are often confronted with the misunderstanding in
our projects that test automation is the silver bullet of
quality. But if it is not clear what is being tested
automatically, there is no confidence in the quality of
the product by the stakeholders.
USE LIGHT WEIGHT EXPLORATORY TESTING
We have great success with using Exploratory Testing in
our projects in a structured way as normal part of our
testing. Very important is to make the scope and result
visible to the whole team.
> E x p l o r a t o r y T e s t i n g v s . T e s t a u t o m a t i o n
You can‘t survive in DevOps
without testautomation

6. > B o o s t y o u r T e s t a u t o m a t i o n
Use Exploratory Testing to know much
better how your product is used
Six steps to improve
› In DevOps one important part is the logging and monitoring
of your system also in production
› Use this to log also your functional user journeys in
production
› Analyze this user journeys and prepare exploratory test
session also out of this knowledge
› Execute these test sessions together with as many feature
team members as possible
› Check, if these user journeys are covered by your automated
tests
› Improve your automated tests with this knowledge, then you
are a step closer the real world usage
› (repeat from step 2) 

7. > S e s s i o n b a s e d t e s t i n g
Pair Testing with the
business department
Bringing the end-users closer to the
feature team
Project setting at a big media company in
Munich, scope with 3 feature teams to
implement the new Content Catalogue
that used for more then 20 TV senders
› Test Session (2 hours) each week
› Same functional scope for the whole
session
› Free to attend from the business side
› Pairing with one person of the business
and one out of the feature team
› Important:
• Documentation of results (also for the
management)
• Debriefing in the audience
DOCUMENT THE RESULTS WITH SESSION-SHEETS
A How-To by Florian Pilz (only in german):
https://www.maibornwolff.de/blog/session-sheets-jira-verwenden

8. > E x p l o r a t o r y t e s t i n g
Exploratory testing in the
project - Facts
Involve the customer earlier into the latest
deployment.
Two feature teams that develops a platform in
the healthcare section which offers several
services for hospital employees.
Implementation of exploratory testing for
customer journeys with business department,
customers and testers.
Test sessions take part every 2-3 weeks.

9. > E x p l o r a t o r y t e s t i n g
Exploratory testing in the project –
Session
• Create customer journeys with stakeholders.
• Define an approximate time for each session, how to
document the results and who participates.
Preparation
• Execute journeys within the specified time.
• Document any relevant findings.
• A debriefing takes place.
• Give feedback on the execution of the customer journeys.
Implementation
• Record the defects and improvements.
• Based on the feedback modify customer journeys.
• Create new regression tests, if necessary.
Evaluation
We don't need a test plan, but we have a plan!

10. > E x p l o r a t o r y t e s t i n g
Advantages of
exploratory tests
in the project
Discover the functional
areas from different
perspectives.
Improve the
customer relationship
through
their participation.
Complete test setup
- for a full test coverage.
Require only a
small amount of time.
10

11. THANKS
for your attention and now: discussion