If you think testing is just an additional step in the process, this block is about how testing makes your product's tech cycle efficient to help you focus on ROI. Just like open-source coding, this is open-source testing. In technical words, it's maximizing value, minimizing waste, and optimizing the testing process to improve efficiency and effectiveness
Lean Approach
If opening this article would have taken more than 2-3 seconds, you'd probably be annoyed. This is the expectation we have now from anything we use. Whether it’s internet speed, instant Google searches, Netflix streaming, or 10-minute delivery, we demand speed and efficiency. First movers have a
Lean Approach
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
Lean Approach
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
Lean Approach
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.
How about if I tell you, Test Driven Development isn’t about testing your code. It’s about designing. I’m not kidding! When you are writing tests, it forces you to think about what kind of interface do you need and how it is supposed to work. If something