Software development, in most circumstances, starts with Optimism and ends with Pessimism. Any Project is initiated with an expectation of delivering considerable value to the end customer. However, when finally delivered, the user may have his expectations unfulfilled and the pessimism sets in. Will the delivered project meets the expectations? Will it work as envisaged? This feature is very important, but not sure whether it has been tested thoroughly and for all possible scenarios?
“To an optimist, the glass is half full.To a pessimist, the glass is half empty. To a good tester, the glass is twice as big as it needs to be.”— Anonymous
As rightly said in the above quote, the role of a good tester is to identify the right size. Testing more for better quality assurance is a pessimistic view and waste of time and resources. On the other hand too less a testing is driven by optimism, but may be a compromise on quality. A Tester need to strike a right balance between the optimism and pessimism to identify the right quality and number of Test Scenarios and Test Cases.
As defined by Peter Thiel in his book “Zero to One: Notes on Startups, or How to Build the Future”, a definite optimist is hopeful of the bright future and has plans for the same. On the other extreme end indefinite pessimist is sure about the bleak future, but no plans to counter it. Striking the balance between Definite Optimism and Definite Pessimism leads the way to “Qualityism”.
How to achieve Qualityism in testing? Or is it just Utopian? Qualityism is strikingly similar to Zero Bug Software. There is no definite point where we can claim to have achieved it. Having said that, moving from pessimism to optimism, QA team can achieve near Qualityism by working on combining and prioritizing the most needed features and the most important parameters within those features. A good combination of this along with scenario planning will ensure that most possible real life user interactions are covered. A thorough execution of testing using the above, will provide a good amount of confidence to the end users. With the limited time and resources available at the disposal for testing, sounds easier said, than done, isn’t it?
@TEST, our Test Management Suite is enriched with features that help in the journey towards Qualityism. Its feature rich and robust Domain Vault has all the functionalities and the attributes that are applicable and required for your product portfolio specific to your domain. @TEST is sturdy, yet flexible to allow the Quality Analysts to add / remove those attributes and combinations for any product or even at a project / sprint level.
Another important feature of @TEST is its ability to generate the Test Scenarios and Test Cases automatically. QA team does not have to spend a good number of hours churning out the combinations for creating Scenarios and Cases to ensure the robust test coverage. These are automatically generated by a combination of algorithms encompassing Test Design Techniques like Boundary Value Analysis, equivalence partitioning, Decision Table and Combinatorial pairs.
Armed with the above Test Cases, the QA process will move from definite pessimism of under-coverage of scenarios to the definite optimism of well-planned and well groomed Test Coverage. @TEST also provides the flexibility to remove or add Scenarios and Cases generated to enable the QA team to have complete control of the QA process to achieve Qualityism.