What to say if someone asks me for test cases?

Here I share my thoughts on how to handle questions around test cases when you have decided to go with an alternative approach.
🌍 My website / blog - nicolalindgren.com
🐦 Twitter - / nicolalindgren
📕 Buy Starting Your Software Testing Career on Leanpub - leanpub.com/startinginsoftwar...
📘 Buy Starting Your Software Testing Career In Amazon - amzn.to/3reJPWr
📙 Buy How Can I Test This? on Leanpub - leanpub.com/howcanitestthis
🍵 Support me here on Ko-fi - ko-fi.com/nicolalindgren
👉 Interested in mentoring? Check out my MentorCruise link: mentorcruise.com/mentor/nicol...
#softwaretesting #testing #qa #qualityassurance #qatester #career #testautomation

[@atkuriajaykumar3701]

Thanks for the information 👍🏻

[@NicolaLindgren]

No problem 👍

[@priyak1111]

The last 40 seconds 👌👍👍👍. Thank you for the video on this topic. Best regards.

[@NicolaLindgren]

Glad you liked it! :D

[@Zaphodikus]

Stakeholders are often asking me how far through the testing are you - and agree, they really want to know what's the likelihood of a showstopper. But since I always prioritise running the harder ones first, It may take a day to get underway, but once we are 50% done, I'm normally sure we have the high-impact ones flushed out. Not all tests cases are equal. And the tester needs to really understand the code churn around functional boundaries and attack those bug "watering holes" first. Very good closing advice, nice to hear confirmation.

[@NicolaLindgren]

Why do you run the harder ones first? Do the harder ones tend to be the ones with higher risk?
Glad to hear you found my video. useful!

[@JensHauser]

I agree that the test cases don´t tell you if there will be any defects but you need to document the outcome of your testing somehow. It could be a charter, test case or a mind map. I think the important information to know is have you mitigated the risks with your testing and are there any areas that you haven´t tested?

[@NicolaLindgren]

One good reason to document your testing (could even be a few notes/sentences on an issue/story etc) is because one's memory isn't as good as one thinks it is.
It's nice to look back and see whether something was missed, or also your thought process before.

[@nameundefinedname5307]

Also could you make a video about test plans and test strategy documents?

[@NicolaLindgren]

Thanks for the idea. At this stage I’m
Not planning to as I don’t think I have value to add in this area

[@NicolaLindgren]

I’ve blogged about test documentation before and for me, I prefer a fairly minimalistic approach.
I like to seriously question why we are create documents in the first place and the value they are supposed to add.
And then assuming we create a test plan etc. then I like to keep it as short as it can be (while still fulfilling its purpose).
nicolalindgren.com/minimalism-and-test-documentation/

[@nameundefinedname5307]

@@NicolaLindgren awesome thank you yes I agree 100%... its just that alot of companies in their job descriptions ask for these skills (writing test plans) (it's usually for roles in smaller companies were they want someone to come in and own testing/ lead roles )

[@nameundefinedname5307]

@@NicolaLindgren e.g
Prepare, review, and maintain testing documents (test plan, test cases, test reports,) to ensure complete test coverage

[@nameundefinedname5307]

Test Cases Are Not Testing! as Mr Bach says I am stuck in a crappy organisation who is obsessed with numbers and test cases! I will be leaving them this year :D

[@NicolaLindgren]

I hope you find a great company you'll be happy at.

[@nameundefinedname5307]

@@NicolaLindgren me too