Pro Membership is required for this event.
Go ProArguably one of the most important parts of an automated test is the assertion(s). Or the oracle, as I prefer. An oracle is a fallible way to identify a problem, put another way, it alerts us to something it believes might be a problem, but it’s not guaranteed to be a problem. Assertions are a method for implementing an oracle.
The reason why I believe they are one of the most important parts is because it’s these assertions that pass and fail. It’s the passing and failing of automated checks that causes most teams to investigate or confirm their next testing steps. But what if I told you that most of your assertions are probably rather poor, and not actually testing what you think you are testing.
In this workshop we are going to explore some common mistakes people make when designing and implementing automated tests. Explore these mistakes, identify better oracles, and in turn design assertions that are guaranteed to add value to your automated tests, and in turn, your testing.
Note: This workshop is a live only event and will not be recorded.
What's Being Covered
After this event you should be able to do the following:
- Define the difference between Oracles and Assertions
- Examine existing automated tests to determine the effectiveness of the oracle
- Discuss why the naming of automated tests is so important when evaluating their value
- Modify existing automated tests to outline a better oracle for the focus of the test
Richard Bradshaw
Schedule
Select a session to learn more about it.
The times below are for
Identifying Codified Oracles In Automated Test Design
When
-What
99 Minute WorkshopDescription
Arguably one of the most important parts of an automated test is the assertion(s). Or the oracle, as I prefer. An oracle is a fallible way to identify a problem, put another way, it alerts us to something it believes might be a problem, but it’s not guaranteed to be a problem. Assertions are a method for implementing an oracle.
The reason why I believe they are one of the most important parts is because it’s these assertions that pass and fail. It’s the passing and failing of automated checks that causes most teams to investigate or confirm their next testing steps. But what if I told you that most of your assertions are probably rather poor, and not actually testing what you think you are testing.
In this workshop we are going to explore some common mistakes people make when designing and implementing automated tests. Explore these mistakes, identify better oracles, and in turn design assertions that are guaranteed to add value to your automated tests, and in turn, your testing.
Takeaways
- Define the difference between Oracles and Assertions
- Examine existing automated tests to determine the effectiveness of the oracle
- Discuss why the naming of automated tests is so important when evaluating their value
- Modify existing automated tests to outline a better oracle for the focus of the test
Prerequisites
Experience with any kind of automated testing is require for this workshop
Speaker

99 Minute Workshops
Short Digestable Live Online Workshops
Live and Instructor-led
All our 99-Minute Workshops are hosted live and led by an instructor.
Short and Targeted
These workshops are a max of two hours long which means they can easy be fit into your busy week. The short time also means they are targeted on a few learning outcomes.
Learn with Others
Connect and learn with other community members during these live online testing workshops.
Available with Pro Membership
All our 99-Minute Workshops are available with Pro Membership, you can attend as many as you like. We also do the odd free workshop with our partners.