Testing Against Implicit Requirements

Talk Description

When I started my testing career, one of my first bosses told me that ASSUME makes an ass out of u and me.  Fast forward almost ten years and those words still  ring true. 

Even if we have written requirements, we will still be expected to test against hidden aka. implicit requirements. And these are a LOT trickier. After all, how can I test against something that I can't see? How can I test against something that nobody has written down or explicitly told me?

When it comes to implicit requirements, there's a lot of room for mistakes, misunderstandings and frustrations - but it doesn't have to be that way.

I'll share my experience in testing against implicit requirements and provide tips on how to spot implicit requirements, what shapes implicit requirements and of course how to test against implicit requirements.

What You'll Learn

• How to spot implicit requirements
• What shapes implicit requirements
• Heuristics on how to test against implicit requirements

By the end of this session, you'll be able to:

Follow

Nicola Lindgren

Quality Engineering Manager

I'm Nicola , a Quality Engineering Manager based in Malmö, Sweden. I'm constantly looking for ways to learn, grow and adapt. In the past, I have worked on projects in various industries including Education, Retail and e-Commerce.I was the founder of the Stockholm Software Testing Talks meet-up and a co-founder of the WeTest Auckland testing meet-up. I was also a frequent co-instructor for the BBST Foundations course. If you want to read my thoughts on software testing, feel free to check out my blog: https://nicolalindgren.com