What is 'Context Driven Testing' in Agile Method?

Answers were Sorted based on User's Feedback



What is 'Context Driven Testing' in Agile Method? ..

Answer / dillip palai

Context-driven testing is a paradigm for developing and
debugging computer software that takes into account the ways
in which the programs will be used or are expected to be
used in the real world. In order to successfully conduct
this type of testing, software developers must identify the
intended market and evaluate the environments in which
people are likely to employ the product. Context-driven
testing is sometimes considered a "flavor" of agile software
development.

A program that works well for one person in a given
situation might prove inadequate or inappropriate for
another person or situation. For example, a word processor
with mathematical symbols and a set of tools for positioning
and manipulating them might be ideal for a college professor
writing a physics textbook but cumbersome and annoying for a
novelist. Conversely, a simple text editor may be preferred
by the novelist but be rejected by the professor.
Context-driven testing revolves around the fact that there
is no single "best solution" that applies to all cases. In
addition, it takes into account the fact that complex
software projects often evolve in unpredictable ways.
Context-driven testing is based on the notion that a
computer program should be treated as a solution. It follows
that if a program does not resolve the problem or situation
it is meant to address, then it cannot be considered a success.

Advantages of context-driven testing include enhanced
user-friendliness of the end product, optimized
functionality for intended users and adaptability of the
product to changing markets and social values. The
context-driven methodology does not necessarily work well in
all situations. Other approaches might prove better for
developers who are under the direct supervision and control
of an autocratic "boss" who takes responsibility for the
results of work done. Context-driven testing would likely
prove superfluous in stable environments where conditions
rarely or never change.

Is This Answer Correct ?    4 Yes 1 No

What is 'Context Driven Testing' in Agile Method? ..

Answer / nilanjan saha

''It is tempting to call context-driven testing "agile
testing" because the principles it recommends are in some
ways analogous to those suggested in the AgileManifesto.
However, agile development is a particular set of values
that belong to one kind of context. Context-driven testing
is broader than that.'' -- James Bach

Is This Answer Correct ?    1 Yes 0 No

What is 'Context Driven Testing' in Agile Method? ..

Answer / nehali

Agile testing technique that advocates continuous and
creative evaluation of testing opportunities in light of the
potential information revealed and the value of the
information to the organization at a specific moment.

Is This Answer Correct ?    1 Yes 1 No

Post New Answer

More QA Concepts Interview Questions

What is Cause and Effect Diagram, how it helps in software testing?.

2 Answers  


Who will write the use case?

3 Answers  


what are the feature of our test group?

0 Answers  


After releasing of the product to the market, it will be a failure, Now tell me whether the testing is a)pass b)fail c) it is partial

6 Answers   AZTEC,


What do you like most about Quality Assurance/Testing?

0 Answers  






why u have choosn testing other than this, what's ur role and responsibilties.

1 Answers   Oracle,


Test plan & test strategy are same..? or they are seprately prepared...?Please clarify

1 Answers  


Hi,i am tester(qa) what technologies i have to learn to enhance my career..

1 Answers  


What is the diff b/w Quality Assurence and Quality Control ?..

11 Answers   FIC, Visualize Technology,


What are the solutions for the software development problem?

0 Answers  


What actually a SQA Tester do in His/ Her first (entry level) Job?

0 Answers  


Need urgent answers for the interview questions? Interviewer asked 1) when you don't have enough requirements spec how did you perform testing? 2) once the project went live if you come to know that there is a bigger defect(bug) what will you do? 3) when there is a bug in the code but not mentioned in the requirement spec( while testing for some other if you come to know this bug) what will you do? I answered these questions but interviewer was not satisfied can any one please tell me the best answers for these kind of situations. I have other interview next week so please provide me the answers or can email me the answers my I'd is tester582@gmail.com. Thanks in advance

3 Answers   Maxwell,


Categories