Context-Driven Testing Methodology
BY samantha.gomez
2 years ago
0 comments comment

The context-driven software testing methodology suggests for continuous and creative evaluation of testing opportunities. It is a testing way that conforms to the context of the project, more than applying a best practice. For context-driven, a good tester should ask as many questions as possible to reveal not only parts of the context but should know about the act of information.

Context-driven methodology is similar to the agile process. It is implemented when the end-users have different preference and needs. Eg: Notepad is an ideal application for writing simple text.
But if other users want the tools to add graphics and different font size and colors, then this application is not for them.
So context-driven testing is based on the fact that ‘no solution is the best solution’. But in this case, the advantage lies with the end user, since the final product that is delivered is a user-friendly product, which is the main aim of Context-driven testing. This methodology works better in stable applications where conditions seldom change and also where test scenarios are not known.

Why do we need Context-driven testing?

Most of the times, programmers are not given a proper well document which explains them exactly how to do the work they are supposed to do, as well as testers also will not be provided with complete documents. So that they would not know the complete proper requirement. But, they may have a spec or a basic document like BRD or some reference documents that tells them what they need to do. But it is assumed they will figure out the best way to accomplish the task. So Context-driven testing is introduced in a situation like this.

Techniques used for Context-Driven Testing

  1. Exploratory testing
  2. Grey Box testing

Seven Principles of Context-driven testing:-

  1. The practice of workflow depends on its context.
  2. There are good practices, but no best practices in context.
  3. People working together are the most important part of the concern project context.
  4. Projects of time overriding in ways that are often not predictable.
  5. The product is a solution in a concept that if the problem is not solved, the product doesn't work.
  6. Good software testing is a challenging process.
  7. Only through judgment and skill, we are able to do the right things at the right times to effectively test our products.

If you need any further assistance, please feel free to get in touch with us.



on 30th May 2012 / by anju.r
A software bug is defined as an error or failure or fault in a system or computer program that produces an unexpected or incorrect result. This is applicable for any Drupal/non-Drupal website. The bug life cycle in a Drupal website consists of steps from identification to closure of a bug. Different stages of Bug Life Cycle are: Drupal Software Testing Leave a reply Your email address will not be published. Required fields are marked *
Leave a reply
Your email address will not be published. Required fields are marked *

Filtered HTML

  • Web page addresses and email addresses turn into links automatically.
  • Allowed HTML tags: <a href hreflang> <em> <strong> <cite> <blockquote cite> <code> <ul type> <ol start type='1 A I'> <li> <dl> <dt> <dd> <h2 id='jump-*'> <h3 id> <h4 id> <h5 id> <h6 id>
  • Lines and paragraphs break automatically.
The content of this field is kept private and will not be shown publicly.
CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.