4.5. Final Takeaways

● Choose testing type based on context, criticality, and frequency

When selecting a type of testing, it's important to consider the context in which testing will occur, the criticality of the application being tested, and how often tests will need to be run. Context may involve factors like the environment, project requirements, or specific characteristics of the application. Criticality relates to how essential the application is for business operations; therefore, the testing type might vary based on its importance. Frequency considers how often testing needs to happen based on updates or changes to the application.

Imagine you are a chef deciding what type of dish to prepare for a dinner party. If the occasion is formal (the project's context), you'd want something exquisite (the criticality). If it's a regular family dinner (low criticality), you might opt for a simple, favorite recipe you can whip up quickly (frequency). Just as a chef chooses recipes based on these factors, testers choose methodologies based on context, importance, and how often they need to cook (test) the application.

● Manual and automation complement each other

Manual and automation testing serve different but complementary purposes. Manual testing allows for human intuition and is better suited for exploratory testing, where testers need to make decisions based on user experience. On the other hand, automation testing handles repetitive tasks efficiently, providing speed and accuracy, especially in regression testing. This means many projects benefit from using a combination of both methods to achieve comprehensive test coverage.

Think of manual testing as a skilled artist who paints a unique picture by hand, focusing on details and creativity, while automation testing is like a factory that churns out high-quality copies of the same painting quickly and efficiently. Just as a gallery might benefit from both original artwork and prints, software testing benefits from the creativity of manual tests and the efficiency of automated tests.

● Functional testing verifies what the app does, non-functional testing verifies how well

Functional testing is concerned with the specific functionalities of an application—essentially, verifying that the app does what it is supposed to do. Non-functional testing, in contrast, assesses performance attributes like speed, usability, and reliability—how well the app works in practical situations. Both types of testing are necessary to ensure a software product not only meets its requirements but also provides a great user experience.

If we think of an app as a car, functional testing would check if the car can start, accelerate, and turn as expected (what the car does), while non-functional testing would assess how smooth the ride is, how fast it can go, and how comfortable it is to drive (how well the car performs). Just like both aspects need to be right for a successful vehicle, both functional and non-functional testing are crucial for software.

● QA should align testing goals with business and technical priorities

Quality Assurance (QA) should not operate in isolation from the business aims and technical framework of a project. This means understanding the overarching business goals and ensuring that the testing strategies contribute towards achieving these targets. It involves regular communication between QA teams and stakeholders to adjust testing approaches based on new business priorities or technical challenges.

Consider a soccer team; the coach must align the team's strategy with the overall goal of winning the match (business goal). If the coach understands the strengths and weaknesses of both the team and the opponent (technical priorities), they can develop a training regimen (testing goals) that ensures the team performs effectively on the field. Similarly, QA teams must understand and prioritize their tests based on business results and technical specifications.

“There’s no one-size-fits-all in testing—choose the right test at the right time for the right outcome.”

This phrase emphasizes that testing should be tailored to the specific needs of each project. There are various testing methods available, and choosing the right one involves considering the unique requirements of the software, its users, and the context in which it operates. The right test might vary from one scenario to another, which is crucial for effective quality assurance.

Imagine a person shopping for clothes. A formal dress for a wedding occasion is different from casual attire for a day at the beach. Just as people choose outfits based on the event and setting, testers must select their testing methods tailored to the application's requirements and its context to achieve the best results.

--