QA Testing With Common Sense
QA Testing With Common Sense
The Experienced Software Testing Journey
Today, organizations are buying into the need for Quality Assurance (QA Testing), also known as Software Testing. But, as we all know, the investment is pricey until the process is built and the return on investment can be seen. In fact, organizations immediately think that automation will solve all their problems. So what do these organizations do? They hire the QA Manager, the testers and expect immediate success. But let’s talk about the reality of software testing.
Software testing can be learned through courses, books, practice but what about the things that are not taught via these methods? This is where QA testing with common sense comes in. What does that mean? Simply put, it means looking at the project that is being tested and using your best judgment to make the right calls. Literally speaking, no project under test is going to be tested 100% because the time that it takes does not align with the time to get the software to market. Let’s use this example.
Organization A wants to create a CRM system that is expected to be released in 90 days. This includes gathering requirements, development, testing and everything else to deliver it successfully. This may or may not be doable. Without short cutting QA testing, Organization A wants to deliver the best CRM ever and obviously defect free. But how? This is where QA leaders, managers with experience and common sense thrive from. This is their opportunity to shine.
QA with common sense is an approach to testing that experienced software testing QA professionals, leaders, and managers learn on the job in order to achieve the ultimate goal – deliver a quality production time. A variety of techniques in testing are used such as prioritization, risk based testing, hybrid methodology approaches, just to name a few. Where common sense comes in is bridging the gap between the organization and the IT team. This is usually done by translating the need for the business to meet the demands of the market and utilizing the best development and testing approaches. Let’s go back to Organization A and their CRM tool.
Let’s suppose that many requirements are either missing or very ambiguous and it’s hard to go back and change what has been done so far. The QA testing manager and testers could probably leverage the need for these requirements by using priority based testing and explaining to the stakeholders what is needed for Day One Implementation. This is definitely common sense. Deliver the sound CRM tool on time but making sure that all Day One requirements are met. Usually stakeholders look at this as a way to work together to resolve the issues but without delaying the release. It’s definitely a WIN WIN approach and conducting QA with common sense.
QA with common sense is really about communication and bridging the gap between any inconsistencies and misunderstandings. It’s about working together, not separate. It offers organizations a way to buy into testing without pointing fingers when things don’t go perfectly to plan and allows the return on investment to be seen. QA testing is about experienced software testing which is acquired during a multi-functional and multi-purpose software testing career . It’s also what makes software testing firms like AwesomeQA stand out from the crowd.