Organisations are starting to recognise the need to not only maintain client-facing systems running 24x7 in production but also keep them releasable to production 24x7. To meet this new demand on software development & testing, we need to put in place a reliable delivery pipeline.
In practice, this means our delivery system needs to follow the same good practices as our software does, incorporating the ability to test changes within a pipeline in isolation, to test for regressions, to understand use cases from both technical and non-technical stakeholders, to decouple the architecture, to reduce the blast radius of failures, to version control our configuration (pipeline-as-code), to secure sensitive information & secrets, to manage tools integration, and to aggregate logging & monitoring.
In this workshop, Manuel Pais will give insights into software releasability and will explain proven patterns and techniques for ensuring software is always releasable, incorporating a delivery chain that is resilient to disasters, scalable and with minimum time to recover from errors.
He’ll show you how to treat a pipelines as a production-grade system in itself, while taking care of the quality of the system with the same rigor as before.
Manuel will also explain how to continuously ensure not only that the pipeline system serves its core purpose of safely progressing our client-facing systems from commit to production, but also that its performance, security, reliability and usability are of the highest standard.
From practical experience, he will present a set of techniques for treating a delivery chain as a first-class citizen in the value stream, including how to compose, scale and monitor a delivery system.
He’ll introduce the concept of building and releasing from zero to production by “release often and recover quickly” and what it implies for testing, covering the following topics:
- Release often and recover quickly.
- Build and release from zero to production.
- Treat a pipeline as a value stream map.
- Treat a pipeline as a production system, including:
- Understand how testing fits into a pipeline for software releasability.
- Understand why software releasability is important for modern software systems.
- Gain practical experience on techniques to treat the delivery chain as a first-class citizen in the value stream.
- Learn about testing, scaling and monitoring the delivery system while maintaining high quality.
Testers, Developers, Project Managers, Product Owners Scum Masters and QA or Development Managers that are interested in understanding how to release software 24x7, incorporating techniques to ensure the quality of our systems, as well as the quality of our delivery pipeline.
Testing is a craft, but it is also and for many foremost a job. A job you do day in day out, evolving with all the rituals every employee develops over time. These rituals, together with all sorts of other external factors (deadlines, pressure, etc.) often means that we don’t have a test strategy or that we are no longer reconsidering the strategies we set out from the start. Having the right strategy in testing is important to stay as efficient and effective as you can be.
In this workshop, Ard Kramer, Beren Van Daele and Andreas Faes want to reignite your strategic fire by placing you in small groups with your fellow testers. Together you will devise a strategy for a real-life product which includes methods, tools, and planning. However, just like in reality, the context will change, and our strategy must change accordingly to aptly react to that change.
The workshop will use the TestSphere cards as a support to spark discussions and for bolstering your strategy.
You will also cover how to:
- Carry out the RiskStorming phase 1, 2, 3
- Create a one-page test plan
- Revise test plans
- Pitch a strategy
Participants of this workshop will learn how to: 1. Work as a team to discuss and describe a strategy to tackle a real-life case and problem. 2. Work out a proposal to convince their manager of tools, methods, and planning. 3. Use the TestSphere cards as help and inspiration.
Testers who are responsible for test analysis and test strategies and need to ensure that test strategies are accepted by stakeholders.
Right-sizing documentation for test design and reporting
Are you getting optimal value from the effort you put into test documentation?
In many organisations, Testers and Test Managers spend excessive amounts of time on heavyweight, expensive documents and scripts that do little or nothing to move their testing forward. Frequently these even impede testing by diverting effort that would be more productively spent thinking about and working with the software.
In some other places, Testers are floundering: trying to adopt a low-documentation approach, but lacking information about what might meet their needs while still giving their stakeholders what they need.
In this interactive workshop, Fiona Charles will work with attendees to explore how to optimise test documentation to meet the needs of each project. You’ll take a thoughtful look at what you can use to:
- Capture your significant thoughts and ideas
- Guide (yourself or others) in moving critical work forward
- Inform your stakeholders so they have opportunities to provide feedback
- Provide useful intelligence about your testing and about the software, so your stakeholders can make informed decisions
- Demonstrate due diligence where required for the record and to satisfy auditors and regulators
Fiona will then help you to examine how others have used mind maps, diagrams, sticky notes, testing logs, and other lightweight media to meet their requirements for optimal test documentation, and how they might work for you. Standard big document templates won’t be completely ignored, but what’s useful within them and what is not, will be discussed. She’ll also show you how to work on strategies for convincing your stakeholders that why it is in their interests to promote optimal test documentation.
Whether your primary goal is to minimize waste or to meet your regulators’ demands, this workshop will help you create test documentation that delivers the best value for you and your business context.
A personal journey into the wonderful world of storytelling
Storytelling is a hot topic, and using storytelling in business settings is becoming more common. Two reasons for this are that we all love stories, and that stories are a centuries old way of communicating. The ancient art of storytelling is a great tool for making our work easier and more fun, and although we are not always aware of it, we are constantly telling each other stories! Stories are a powerful and effective way of transferring your vision, strategy or approach and we can benefit from them in the way we work in agile teams.
Good stories surprise us as they have compelling characters. They make us think and make us feel. They stick in our minds and help us remember ideas and concepts in a way that numbers and text on a slide with a bar graph don’t. Storytelling increases the impact we can have within our organisations. Stories make presentations better. Stories make ideas stick. Stories help us persuade!
For the first part of this interactive and fun workshop, Huib Schoots & Alex Schladebeck will focus on what storytelling is, using several techniques. Then they’ll focus on the practical use of stories; showing how they can be used for testing, reporting, user stories, and to obtain project vision as well as cross-project communication.
The following topics will be covered:
- Introduction & learning goals
- Examples of great stories
- What makes a good story?
- What is storytelling?
- Types of stories
- Story elements
- Building a climax
- Why storytelling & why stories matter?
- Science of Storytelling
- Storytelling Techniques
- How can you use storytelling in your daily work?
- Storytelling in testing: The Testing Story
- Storytelling in your project: Story meetings
- Storytelling in practice
- Wrap-up & takeaways
During the workshop, you’ll get the change to practice your skills in many fun exercises!
From this workshop, you will learn what storytelling is and how to use storytelling for your day-to-day testing activities to convince, to structure, to inspire and to help you reach your goals. The concept will take you above and beyond "user stories" and will serve much more than a communication tool for all aspects of project work (and life!). Storytelling will also help you to develop your imagination, which will empower you to solve problems and consider new and inventive ideas.
You will learn to use the power of listening and speaking to create artistic pieces of art to transfer a clear and concise message! You will gain the basic skills to tell great stories to gain confidence and experience that telling stories is not as hard as it sounds, it is just great fun!
Testers, Developers, Business Analysts, Product Owners, Scrum Masters and QA or Development Managers that want to understand to how to use storytelling as a technique and tool for working in Agile environments.
Test Automation, Don't just do it! - Why the Nike approach to test automation is going to get you in trouble and what you can do about it
If you are a tester or a developer keen to start doing test automation, this workshop is for you! It is a widespread belief, that with test automation you just must learn to code (Seretta Gamba calls code also the actions that more modern tools sell as ‘no-coding’) and you can start right away. Unfortunately, that is usually a sure way to get into big trouble as soon as you need to update your automated tests (and that happens every time the System Under Test gets a new release!).
In this workshop, Seretta will show you, with eye-opening examples, what can happen. Such problems have long been solved by experienced practitioners and their solutions have been collected by Seretta and Dorothy Graham in Test Automation Patterns. The second part of the workshop will introduce you to the Test Automation Patterns Wiki, and will explain how to use it as well as trying it out with intuitive exercises.
You will not learn to code, but you will learn what distinguishes an excellent Test Automation Engineer from being just one more regular Test Automation Engineer. Developers, on the other hand, will notice that knowing how to code is no guarantee for good test automation. For this workshop, it’s immaterial if you work in an agile environment or not! What Seretta intends on doing is to show Testers or Developers, who want to do system test automation, how to become not just Test Automation Engineers, but ‘excellent’ Test Automation Engineers!
Contrary to what some managers believe, and some vendors want you to believe, test automation is not done by just procuring a tool and telling people to start coding! In the beginning one usually concentrates on automating as many test cases as possible and doesn’t really ‘waste time’ to define a strategy to render those automated tests also maintainable, scalable, repeatable and so on. Also, testers usually automate test cases just as they performed them manually. In agile, on the other hand, there is often the danger that different teams do test automation independently and don’t notice that each, in his own way, is inventing the same wheel!
Using intuitive exercises, Serreta intends on demonstrating what happens in such cases. Of course, getting to know what kind of problems can come up, is just half the battle, so she will introduce the Test Automation Patterns Wiki, a collection of expert solutions to most of the current automation issues. With a new batch of exercises, you will learn how to navigate and use the wiki to solve some of the problems discovered with the first exercises.
Finally, together you will look at the most important patterns along with some aspects of special interest, namely:
- Whole team approach - Maintainable testware - Good programming practices Abstraction levels Design for reuse - Independent test cases Object map - Fail gracefully - One clear purpose - Testware architecture - Tool independence - Test automation owner - Think out-of-the-box - Keyword-driven testing
During the workshop, you will carry out the following exercises:
1. Given a simple specification (making tea?), you will write the instructions for the ‘tool’ to execute. Swapping instructions, you will try, as ‘test automation tools’ to execute them. You will also learn not only that to drive a tool they need to write precise instructions (tools are stupid!), but also that instructions must be clear and documented so that other Test Automation Engineers can read or maintain them.
2. The original specification is changed and you’ll update their instructions. The ‘test automation tools’ execute them. Participants learn that ‘spaghetti code’ is not easy to maintain.
3. A ‘manual test’ specification must be ‘automated’. You’ll learn that test cases need (should) not necessarily be automated.
4. You will discuss, in groups of 4, what the main issues found in the previous exercises are.
5. Then, using the diagnostic feature in the wiki, you’ll check if the wiki leads them to the same issues.
6. Finally, you will examine and discuss the patterns suggested in the wiki to solve the issue(s) found the previous exercise.
7. After having looked up the patterns maintainable testware and good programming practices, you’ll rewrite the instructions to the original specification and learn how to break up a specification in more manageable and maintainable chunks.
8. Using the pattern Keyword-Driven Testing, you’ll update the instructions from exercise 3 to contain the changes from Exercise 2 (first batch) and realize how much easier it becomes when instructions are written modularly.
9. Adopting the pattern think out-of-the-box you’ll rewrite the instructions using features of the test automation tool and realize how powerful automation can be compared with manual testing.
- Gain a good understanding of what is important for efficient and long-lived test automation.
- Learn to navigate and use the test automation patterns wiki, giving them a tool that they, and their team, can use again and again.
Testers or Developers who want to become excellent at test automation (no previous experience in test automation is required).