{"id":3036,"date":"2020-06-16T13:27:01","date_gmt":"2020-06-16T12:27:01","guid":{"rendered":"https:\/\/www.brainbox.consulting\/?p=3036"},"modified":"2020-08-27T09:32:07","modified_gmt":"2020-08-27T08:32:07","slug":"an-introduction-to-context-driven-testing","status":"publish","type":"post","link":"https:\/\/brainbox.consulting\/talent\/an-introduction-to-context-driven-testing\/?lang=nl","title":{"rendered":"An Introduction to Context Driven Testing"},"content":{"rendered":"

What is Context driven testing?<\/strong><\/h2>\n

The context-driven testing is a model based on the context of the project rather than going by books methodology testing or some fixed notion of best. It recommends testers to choose their testing techniques, test deliverables, test documentation and test objectives by looking into the details of a specific situation. Context-driven software testing is not a testing technique, it is a set of values about test methodology.<\/p>\n

With this type of testing there is no single best practice that applies to all cases. Its value is contingent upon the amount of useful and timely information gathered during the testing process and its success depends on whether the software solution resolves the problem or situation it is intended to address.<\/p>\n

Context-driven testers define their testing objectives, techniques, and deliverables by identifying the details of the specific situation such as desires of the stakeholders who commissioned the testing. The key strength of context-driven testing is project-appropriate application of skills and judgement rather than conventional methodologies.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Basic Principles of Context driven testing:<\/strong><\/h2>\n

According to Cem Kaner, Brian Marick, James Bach and Bret Pettichord, the founders of Context driven school, the 7 basic principles in context driven testing are,<\/p>\n

    \n
  1. The value of any practice depends on its context.<\/span><\/li>\n
  2. There are good practices in context, but there are no best practices.<\/span><\/li>\n
  3. People, working together, are the most important part of any project’s context.<\/span><\/li>\n
  4. Projects unfold over time in ways that are often not predictable.<\/span><\/li>\n
  5. The product is a solution. If the problem isn’t solved, the product doesn’t work.<\/span><\/li>\n
  6. Good software testing is a challenging intellectual process.<\/span><\/li>\n
  7. Only through judgement and skill, exercised cooperatively throughout the entire project, are we able to do the right things at the right times to effectively test our products.<\/span><\/li>\n<\/ol>\n

    Context driven testing <\/strong>vs Standard testing<\/strong><\/h2>\n

    A traditional testing process in general follows a series of standard steps mentioned below to complete the testing,<\/span><\/p>\n

      \n
    • Requirement analysis<\/span><\/li>\n
    • Test Planning<\/span><\/li>\n
    • Test documentation \u2013 test scenarios, test case development<\/span><\/li>\n
    • Test environment setup<\/span><\/li>\n
    • Test execution<\/span><\/li>\n
    • Test reporting<\/span><\/li>\n<\/ul>\n

      These steps are decided based on the best practices, QA standards, industry guidelines etc. Now there is nothing wrong with this process. It will work fine and give the desired end result, as this is a time tested and standard approach. But if we raise a question whether this approach gives way for an optimal result, then the answer may be ‘doubtful’.<\/p>\n

      On the other hand context driven testing does not advocate following a set of same steps for every projects. As the name suggests, context driven testing gives more importance to the current context of a specific project rather than blindly following an established method\/process. Because every project we deal with has different circumstances like,<\/span><\/p>\n