Abstract: How can I use exploratory testing on something that does not have a GUI?
Exploratory testing is a systematic approach for discovering risks using rigorous analysis techniques coupled with testing heuristics. A lot of times we test before there’s a graphical user interface or finalized features available, and exploring is the mindset that helps us uncover things we do not know. Still I often hear people expressing surprise at the idea that you can explore an API. Something that is intended for programmers.
In this session, we will work together in a mob with one computer to learn about exploratory testing of an API. We’ll look at exploring usability of an API (also known as “design”), internal and environmental variables we can tweak, and prioritizing information we will find relevant in relation to it’s purpose. Let’s work on code-oriented tests that are not regression oriented but aim at finding new information by means of exploratory testing.
Learning Outcomes: - Uncover how other people think when testing to learn from your peers
- Learn to identify variables (things you can change) on an API or a method signature
- Learn to prioritize your testing efforts for most relevant feedback fast
Attachments:
