Recognizing appropriate scenarios for context testing

Recognizing appropriate scenarios for context testing

In what situations would it be appropriate to use context testing?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the most relevant information on Agile development, application security, testing & QA, software requirements, and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSoftwareQuality.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSoftwareQuality.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Imagine you have a website to test and some of your test ideas are centered on different browsers, different versions of flash and mobile accessibility. Now for a moment, imagine your project has changed and you are testing the migration of customer data that includes sensitive tax information. Your tests may become centered on data security and encryption in the new environment. These are two different situations, each situation is unique and each brings to mind different test ideas. These ideas are based on the context of what you are testing. When you are focused in one situation, your test ideas, tools and approaches may be focused in a unique way that makes sense for your project needs. When you switch the project, your needs shift as well. In short, I cannot envision a situation where context-driven testing would not apply.

This was first published in October 2009