TESTING IS CONTEXT DEPENDENT
Testing is context-dependent. Testing is done differently in different contexts.
As part of the Seven Testing Principles of the ISTQB Foundation Level Syllabus, on the context-dependent principle.
“Testing is done differently in different contexts. For example, safety-critical industrial control software is tested differently from a mobile e-commerce app. As another example, testing in an Agile project is done differently than testing in a sequential software development lifecycle like in a waterfall methodology.” ISTQB Foundation Level Syllabus
You can’t just take the advice from one testing blog or article and apply it to all of your tests. To be efficient and effective, you have to tailor your approach to the context of your situation. In this blog post, we’ll look at the various contexts in which software testing happens and discuss how you can tailor your approach accordingly. Let’s dive in!
There are some commonalities; however, that is important to keep in mind when doing any form of testing.
First, testing is an essential part of the software lifecycle and is not an activity that can be done after the software is complete.
Second, testing is a critical, non-negotiable part of the software lifecycle. Testing cannot be minimized or marginalized.
Third, testing must be integrated into the software lifecycle.
Since testing is done differently in different contexts, it is helpful to understand the underlying principles of testing. There is value in knowing what all forms of testing share in common. There are benefits to understanding the basics of testing. By understanding the basics, you can apply them where they are most needed.