General opinion: There's a hyped term - go into the user's shoes and you'll make what they would like. Then, you can run campaigns to verify certain hypotheses, take surveys, have interviews, etc. Or see from analytics what could have happened. Or the best - Once delivered, it’s done.
General opinion: Five mins? Five days? (Dare I say it) I have no idea, we sit until it’s found out. This must have happened when your production would have gone under crisis. The whole team would have come up forming a crew to fix up. Alternate opinion: If your
General opinion: That’s the feature - planned. It will take me X no of days to implement the feature - implementation. For fixing the mess-ups a day more added - buffer. Deadline: X+1 days. Alternate opinion: If my colleagues at GreyB would be your QA. Bye-bye, your deadline.
Choose one - 60 test case or 10 for one function? General Opinion: More the test cases, better the code. So, 50. Alternate Opinion: If you choose 50, It’s better don’t spend time on writing test cases, just do the development rather - it would be less waste
Situation: I can access this after being even when my access is revoked. Problem: You missed a check in a function. General opinion: Add the missing condition in that function and push it to production. Time took to fix: A few mins - Quick approach Impact level of the fix:
It's similar to open source libraries, which are open telling about some extent in generic ways. Then, why not tests? Test teams establishing stuck on planning how to setup, it's about sharing that. It's about sharing how someone can test using similar strategies and not exactly the test suites.