The best way to start a war is to have no common ground. It is the same for software testing. If you and your colleagues have different thoughts about the basics of testing, you are bound to fail.
Creating software products is not without risk. Identifying risk and identifying the right actions to take can save a headache.
In case testing is part of those actions to mitigate risks, it is essential to define mandatory, recommended, and optional actions.
We test. You test. Yet, the resulting quality is not the same. Why?
Shouldn’t software testing be a quality stamp on the software product?
What you think of software testing is not the same as what your client thinks of testing, what a regulator thinks of software testing, etc.
What software testing means depends on the person you ask, but how do you create a situation in which all stakeholders are at least aligned and think the same way about software testing?
Thaste It started developing Bona Iqiniso, because it got more and more involved in projects to introduce testing in Agile development. One thing became very clear, that most companies would introduce testing as part of software devlopment according to the Agile principles, but didn’t realize the ripple effect this has on the organization. That’s why Bona iqiniso, which means “realize the truth” in zulu, came to life to make companies aware that testing is not only to realize the truth about the software products they were creating, but also to make them realize the truth about the impact testing has on the organization.
