Deepak asks, “Hi Debasis, dainty articles. I tried searching for context-driven testing but couldn't uncovering whatever article. I am novel to testing in addition to desire to pursue my career inwards testing, a piddling scrap almost me. I desire to know the framework for context-driven testing. Is it possible to write an article w.r.t the above-mentioned framework? Thanks whatever way. It is a pleasance reading your article (although I bring read only 1 article)!”
Can y'all pick out the mutual thing inwards the inwards a higher house three questions? Do y'all bring answers to whatever of the inwards a higher house FAQs? If your respond is No, thence read on. In instance your respond is Yes, thence this post powerfulness live intended for testers similar you, hold reading!
What is a ‘context’?
The WordWeb lexicon of my desktop calculator defines a “context” every bit “The laid of facts or circumstances that surround a province of affairs or event”. definition apart, a context is the circumstances relevant to something nether consideration. It is the background data that enhances agreement of technical in addition to work organisation environments to which the work relates.
What is ‘context-driven testing’?
The context-driven testing is oft considered every bit a season of Agile Testing that recommends continuous in addition to creative evaluation of testing opportunities inwards lite of the potential data revealed (mostly past times context-based questioning) in addition to the value of that data to the arrangement correct now! It tin live defined every bit testing driven past times an agreement of the environment, culture, in addition to intended move of software. For example, the testing approach for life-critical space-ship command software (remember Columbia disaster?) would live completely dissimilar than that for a low-cost payroll processing software.
A MD does non move a chopper (that a butcher uses) piece operating a patient. Instead, he uses a scalpel. Both the chopper in addition to the scalpel are precipitous knives in addition to are meant for cutting but they can’t supersede each other in addition to has their move inwards their ain specific areas (contexts). Neither a chopper tin live used for operating a patient nor a scalpel tin live used for slaughtering a pig! As the context changes, the effectiveness of the equipments (practices/approaches) also changes. So at that spot is zilch such thing similar one-approach-fits-all! Approaches demand to modify alongside the modify of province of affairs in addition to modify inwards circumstances.
As James Bach puts it - “Context-driven” way to jibe your solutions to your problems every bit your problems change. Good do is non a affair of popularity. It’s a affair of science in addition to context.
I believe that, context-driven testing starts alongside context-driven thinking! Context-driven testers never seek to fit inwards the same solution to dissimilar problems in addition to however promise that they would eventually succeed! Rather they seek to uncovering a dissimilar solution that powerfulness solve the novel work in addition to follow it! Remember, at that spot is no “master key” (best do that succeeds inwards *every* cases, no affair what is the context) inwards software testing. [Master primal is a primal that secures entrance everywhere past times plumbing equipment into multiple locks!]
The Seven Basic Principles of the Context-Driven School!
1. The value of whatever do depends on its context.
2. There are adept practices inwards context, but at that spot are no best practices.
3. People, working together, are the most of import business office of whatever project's context.
4. Projects unfold over fourth dimension inwards ways that are oft non predictable.
5. The production is a solution. If the work isn't solved, the production doesn't work.
6. Good software testing is a challenging intellectual process.
7. Only through judgment in addition to skill, exercised cooperatively throughout the entire project, are nosotros able to create the correct things at the correct times to effectively examine our products.
Context-driven testers concord alongside these principles in addition to follow them piece solving testing problems! In instance y'all are interested inwards knowing almost other schools of software testing y'all powerfulness reckon reading this post past times Dr. Cem Kaner.
What a context-driven tester similar me powerfulness create when allotted to a testing assignment?
1. H5N1 context-driven tester powerfulness showtime past times bespeak a bunch of context-based/context-related questions inwards an endeavor to know the context improve in addition to deduce data almost the mission, aims in addition to objectives of the testing assignment! As it is said, proper questioning has the capability of solving one-half of the problem; in addition to a context-driven tester knows this fact clearly from his sense in addition to practice!
2. Once somebody said - The only thing that does non modify inwards this the world is “the give-and-take change” itself! This applies to software evolution too. Projects hold changing shapes every bit the evolution stage continues. H5N1 smart context-driven tester knows in addition to understands that it is wise to live flexible in addition to modify the testing strategy every bit the context changes during a evolution phase. He tin modify hear in addition to modify the way he thinks in 1 lawsuit he realizes that the context has changed in addition to is non the same every bit it was before!
3. H5N1 context-driven tester understands that the testing practices/approaches/procedures that had worked inwards his before testing projection powerfulness or powerfulness non piece of work inwards the electrical flow assignment exactly because the context of both these projects powerfulness non live the same! H5N1 context-driven tester clearly knows that what looked similar the “best practice” (so called!) inwards the before projection powerfulness of a precipitous unloose its value in addition to move a “bad practice” in 1 lawsuit the context is different!
4. H5N1 context-driven tester also understands that context-driven testing is a laid of values rather than a physical care for or technique. It revolves roughly the fact that software users are human beings alongside various preferences, needs, abilities in addition to limitations. H5N1 plan that plant good for 1 mortal inwards a given province of affairs powerfulness show inadequate or inappropriate for some other mortal or situation.
“Survival of the fittest” [Charles Darwin has called it every bit 'natural selection', or the preservation of favored races inwards the scrap for life inwards his theories of evolution inwards the mass “The Origin of Species”] is a phrase that refers to the physical care for past times which favorable traits that are heritable move to a greater extent than mutual inwards successive generations of a population of reproducing organisms, in addition to unfavorable traits that are heritable move less common! In other words, those who are improve equipped alongside the powerfulness of adaptation move in addition to the balance perish! In a software evolution surround where the context is unstable in addition to is probable to change, the testers those are improve trained to adapt themselves in addition to modify gears alongside the changing context bring a improve run a peril of success than those who are unable to create so! It is all almost adjusting yourself (the tester) to the province of affairs than to adjust the province of affairs every bit per your comfort level! We can't modify this world. The the world won't modify until nosotros change. The questions are:
» "Will nosotros change"?
» “Are nosotros prepared to evolve”?
» “Are nosotros prepared to modify our practices in addition to approaches to testing when the context has changed”?
» “Are nosotros prepared to halt expecting whatever best do to come upwards to our rescue in addition to create wonders for us fifty-fifty when the context inwards inquiry is exclusively dissimilar from the instance where these practices had been successful”?
What create y'all think? Do y'all allow the *context* drive your testing approach or the *best practices*? I am excited to hear your views. It is fourth dimension to instruct song in addition to allow out your views/opinions past times commenting.
Happy Testing…
More interesting articles here :Tutorial Software Sumber : http://www.softwaretestingtricks.com/
Can y'all pick out the mutual thing inwards the inwards a higher house three questions? Do y'all bring answers to whatever of the inwards a higher house FAQs? If your respond is No, thence read on. In instance your respond is Yes, thence this post powerfulness live intended for testers similar you, hold reading!
What is a ‘context’?
The WordWeb lexicon of my desktop calculator defines a “context” every bit “The laid of facts or circumstances that surround a province of affairs or event”. definition apart, a context is the circumstances relevant to something nether consideration. It is the background data that enhances agreement of technical in addition to work organisation environments to which the work relates.
What is ‘context-driven testing’?
The context-driven testing is oft considered every bit a season of Agile Testing that recommends continuous in addition to creative evaluation of testing opportunities inwards lite of the potential data revealed (mostly past times context-based questioning) in addition to the value of that data to the arrangement correct now! It tin live defined every bit testing driven past times an agreement of the environment, culture, in addition to intended move of software. For example, the testing approach for life-critical space-ship command software (remember Columbia disaster?) would live completely dissimilar than that for a low-cost payroll processing software.
A MD does non move a chopper (that a butcher uses) piece operating a patient. Instead, he uses a scalpel. Both the chopper in addition to the scalpel are precipitous knives in addition to are meant for cutting but they can’t supersede each other in addition to has their move inwards their ain specific areas (contexts). Neither a chopper tin live used for operating a patient nor a scalpel tin live used for slaughtering a pig! As the context changes, the effectiveness of the equipments (practices/approaches) also changes. So at that spot is zilch such thing similar one-approach-fits-all! Approaches demand to modify alongside the modify of province of affairs in addition to modify inwards circumstances.
As James Bach puts it - “Context-driven” way to jibe your solutions to your problems every bit your problems change. Good do is non a affair of popularity. It’s a affair of science in addition to context.
I believe that, context-driven testing starts alongside context-driven thinking! Context-driven testers never seek to fit inwards the same solution to dissimilar problems in addition to however promise that they would eventually succeed! Rather they seek to uncovering a dissimilar solution that powerfulness solve the novel work in addition to follow it! Remember, at that spot is no “master key” (best do that succeeds inwards *every* cases, no affair what is the context) inwards software testing. [Master primal is a primal that secures entrance everywhere past times plumbing equipment into multiple locks!]
The Seven Basic Principles of the Context-Driven School!
1. The value of whatever do depends on its context.
2. There are adept practices inwards context, but at that spot are no best practices.
3. People, working together, are the most of import business office of whatever project's context.
4. Projects unfold over fourth dimension inwards ways that are oft non predictable.
5. The production is a solution. If the work isn't solved, the production doesn't work.
6. Good software testing is a challenging intellectual process.
7. Only through judgment in addition to skill, exercised cooperatively throughout the entire project, are nosotros able to create the correct things at the correct times to effectively examine our products.
Context-driven testers concord alongside these principles in addition to follow them piece solving testing problems! In instance y'all are interested inwards knowing almost other schools of software testing y'all powerfulness reckon reading this post past times Dr. Cem Kaner.
What a context-driven tester similar me powerfulness create when allotted to a testing assignment?
1. H5N1 context-driven tester powerfulness showtime past times bespeak a bunch of context-based/context-related questions inwards an endeavor to know the context improve in addition to deduce data almost the mission, aims in addition to objectives of the testing assignment! As it is said, proper questioning has the capability of solving one-half of the problem; in addition to a context-driven tester knows this fact clearly from his sense in addition to practice!
2. Once somebody said - The only thing that does non modify inwards this the world is “the give-and-take change” itself! This applies to software evolution too. Projects hold changing shapes every bit the evolution stage continues. H5N1 smart context-driven tester knows in addition to understands that it is wise to live flexible in addition to modify the testing strategy every bit the context changes during a evolution phase. He tin modify hear in addition to modify the way he thinks in 1 lawsuit he realizes that the context has changed in addition to is non the same every bit it was before!
3. H5N1 context-driven tester understands that the testing practices/approaches/procedures that had worked inwards his before testing projection powerfulness or powerfulness non piece of work inwards the electrical flow assignment exactly because the context of both these projects powerfulness non live the same! H5N1 context-driven tester clearly knows that what looked similar the “best practice” (so called!) inwards the before projection powerfulness of a precipitous unloose its value in addition to move a “bad practice” in 1 lawsuit the context is different!
4. H5N1 context-driven tester also understands that context-driven testing is a laid of values rather than a physical care for or technique. It revolves roughly the fact that software users are human beings alongside various preferences, needs, abilities in addition to limitations. H5N1 plan that plant good for 1 mortal inwards a given province of affairs powerfulness show inadequate or inappropriate for some other mortal or situation.
“Survival of the fittest” [Charles Darwin has called it every bit 'natural selection', or the preservation of favored races inwards the scrap for life inwards his theories of evolution inwards the mass “The Origin of Species”] is a phrase that refers to the physical care for past times which favorable traits that are heritable move to a greater extent than mutual inwards successive generations of a population of reproducing organisms, in addition to unfavorable traits that are heritable move less common! In other words, those who are improve equipped alongside the powerfulness of adaptation move in addition to the balance perish! In a software evolution surround where the context is unstable in addition to is probable to change, the testers those are improve trained to adapt themselves in addition to modify gears alongside the changing context bring a improve run a peril of success than those who are unable to create so! It is all almost adjusting yourself (the tester) to the province of affairs than to adjust the province of affairs every bit per your comfort level! We can't modify this world. The the world won't modify until nosotros change. The questions are:
» "Will nosotros change"?
» “Are nosotros prepared to evolve”?
» “Are nosotros prepared to modify our practices in addition to approaches to testing when the context has changed”?
» “Are nosotros prepared to halt expecting whatever best do to come upwards to our rescue in addition to create wonders for us fifty-fifty when the context inwards inquiry is exclusively dissimilar from the instance where these practices had been successful”?
What create y'all think? Do y'all allow the *context* drive your testing approach or the *best practices*? I am excited to hear your views. It is fourth dimension to instruct song in addition to allow out your views/opinions past times commenting.
Happy Testing…