Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.

Misma Silfver | Comments

Displaying all 3 comments
What's the hardest part of defining "expected behaviour" for a system that produces different output every time? image
Liked this, like a coach, just asking questions, no answers. Food for thought.
Lessons for software testers from three great Western philosophers image
Oh I love it, had not thought about this angle, thanks for sharing these insights! I did Philosphy 101 in high school and that is the extend of my experience on this. So seeing how you tie these to software testing is really fun and cool! Bit like critical thinking content, courses I recommend to all testers in our company. Nothing to do with Playwright or Postman. :-D There is this kind of cross "industry" lessons one can find in almost everywhere when you read with thinking hat on.
So Apparently I've Been Using Claude Wrong This Whole Time image
I've been using the "let it take notes" but in the context of creating my personal use FPL application. To keep note of the architecture decisions. I think I will extend it to the tipped test framework docs too as things have gotten wee bit unwieldy lately as I have tried to change databases. :)
Misma Silfver profile image
Misma Silfver
Senior Quality Consultant
Subscribe to our newsletter