Breakfast #3: Requirements in AI world

Helsinki Testing Breakfast — Meetup #3: working with requirements & AI.

We've all been there: a ticket with three words, a Figma link that's two versions old, and a deadline tomorrow. So we figure it out ourselves. We always do.
But is that fine? Should testers just accept that requirements are broken — or should we be pushing back harder? And now that AI can generate acceptance criteria in seconds, does that change anything? If change - is it a positive change?

This Friday over coffee, let's dig in:

• When there are no requirements, how do you decide what to test?
• Are AI-generated requirements actually testable — or just more noise?
• How do you raise quality concerns when "move fast" is the answer to everything?
• What's the tester's role when the spec is vibes and a Slack message?

All experience levels welcome — whether you've been testing for 6 months or 16 years, you've learned something worth sharing.
See you!