06 Jun
As my five-year journey in software testing comes to a close and the sixth year begins, I want to take some time to document the roadmap to achieving what has worked for me so far. I call it the “5 Pillars of Software Testing Mastery.” These are five pillars that have helped me stand out in my career as a software tester. These are not just “concepts”; they are practical strategies that you can incorporate into your testing activities from end-to-end functional tests to automation. Let’s dive in!
Â
- Understanding Test Basis
The test basis defines the scope of what needs to be tested. This includes requirement documents, such as Business Requirement Documents (BRDs), Product Requirement Documents (PRDs), use cases, design specifications, and user stories. Requirement documents set the criteria against which the software’s functionality and behavior are evaluated. As a Tester you can use these criteria to verify that the software complies with the specified requirements. It’s crucial for testers to understand these documents and create a clear link or traceability between your test findings and the requirements. This link provides proof that you’ve covered all aspects of the product as specified in the document. Thoroughly understanding the requirement document enables you to create test cases that cover both functional and non-functional aspects of the software, enhancing test coverage and completeness. Think of these documents as the “bible” for your product.
There are five areas that we encourage CMOs to look at. The first is, what are my future-back platforms that will lead growth for the next 5 to 10 years? Taking today’s profit pools and forecasting them present forward just won’t capture the level of disruption that’s impacting these industries.
- Test Planning and Strategy
- Writing Detailed Test Cases/Scripts
I call well-written and documented test procedures the backbone of effective testing. Don’t just write test cases to fill up lines, write test cases that uncover defects. Here’s my theory: “When you execute a test case/script, and it passes, that test has failed to find any defects.” Remember, every test case/script is like a detective on a mission to find a bug. We know there’s always a bug, the question is, where is it? Ensure your test cases cover the most critical aspects of the application under test. Failing to do so sets you up for trouble. Also, consider reusability, especially in Agile and DevOps environments. In my five-years journey I have tested over 100 application updates on mobile applications only! (Thanks to the Nigerian FinTech space) So reusing test cases or scripts allows me to save valuable time and resources. Instead of creating new tests from scratch for each software update, I can leverage existing cases and scripts. Reusability ensures that test coverage is maintained and testing cycles are completed more efficiently, making the testing process cost-effective and productive. But beware of Pesticide Paradox! oftentimes, old test cases fail to catch new defects which is why it’s crucial to regularly update your tests to keep them relevant and effective.
- Proper Test Documentation
- Communication
Effective communication is key in software testing. Testers often bring “not-so-great” news to the table, such as “There’s a bug here.” However, effective communication is essential to maintain a productive and positive working relationship with developers. Testers and developers share the same mission âdelivering functional and quality solutions to customersâ. So, why create unnecessary friction? Be respectful, kind, constructive, and reasonable in your communication, but above all never compromise quality. Clear and respectful communication reduces misunderstandings between testers and developers and ensures that developers accurately understand the testing team’s findings and expectations. Good communication enables productive discussions, issue resolution, and collaboration to improve software quality.
As a bonus point, remember that âit’s okay not to know everythingâ. In the ever-evolving field of technology and quality assurance, there will always be something new to learn. Spoiler Alert âYou will never know everything!â. Embrace your mistakes, errors, and failures, as they are part of the learning process. Give yourself the grace to grow, and you’ll eventually gain confidence in your skills.
Thank you for reading this article, and please feel free to reach out if you have any questions or feedback. You can also follow me on Instagram, Twitter and Linkedin for more insights and updates.
