Posted by
Amit Kulkarni [Admin]
| Posted in
advoocate
,
approach
,
CDT
,
Context-Driven testing
,
Suggestions/Feedback
,
test cases
,
test plan
,
test suite
| Posted on
9/07/2009 12:05:00 AM
I love reading blogs......as I get to learn some good things, at times I get to read a chance of funny story, the way these bloggers are portraying the skills of writing (the most important of all). How do you express yourself?
I have this friend of mine asking me to post something on "Context-Driven Testing" for many days.
So here we go.....
In our day-to-day life....we follow the same procedure while doing so called "TESTING". We have a script ready with us or set of test cases/test suites and we just have to run/execute them all successfully and record the bugs if any.
What do you think - the procedure is more important or the way we test it?
This can be argued by many and I am not here for any argument but would like to second my support to the concept of testing where we do not follow any procedure but would like to see how the software works? These is what Context-Driven testing is all about. You would like to see how it looks or how it works rather than going through a piles of files or documentation.
Context-Driven testing--believes in a way that conforms to the context of the proejct as opposed to the traditional way. Good testing is a part of good testing skills and not any procedure. It just to focus on human context (keeping the end user in mind) than a routine procedure.
There are some things which a "Context-Driven tester" would say on this:
1. What is most important "the end user" or the procedure/tools which we all use?
2. Do you believe in specifications or would like to see or rather directly work on the app?
3. Value added Suggestions/Feedback over the same old routine of completing the testing for sake.
4. We would like to see something new....in a software with more features even if that is out of scope but then 'Why not?'
These people are more passionate, excited, creative and lotz of enthu. They would love to work freely rather than sticking to the same old procedures, plan (which is ofcourse important but can be considered when required) These bunch of people would have so many creative ideas, suggestions which are not mentioned in any document but they can certainly add a value to the app. These people are not sideling the old procedure but they are keeping in mind that things which are going to change in future. These people are ready for any situation with broad and deep awareness of problems in a project with possible testing solutions to these problems.
Some key things about these people:
- Documentation is not always necessary. Good testers knows how to work with the whatever information they have with them. If required additional information for anything then these people will be very specific about "What they are looking for?"
- Quality does matter to these people - whether it provides useful and timely information.
- Not stick to the "Quality Assurance" but believe in testing is providing information to all.
- No test plan. No test documents. These people do not make excuses of these things.
- Like an "Advocate" defending the clients case..... these testers will defend the app under test from user's perspective.
- Exploratory Testing
- GrayBox Testing
If we all follow the same old procedure then chances are more that -- users will come up with defects in your app. If we start thinking like users, their value added feedbacks then we are going one step ahead of the time -- which will give some breathing space to a user. It is not possible to cover all the scenarios as user might think of but atleast we are trying to cover them.
For more reading you may want to check the following links:
If you have differences of opinion or interpretations with what is stated above then you are most welcome to post your comments.
Best Regards,
Amit
testing is my passion!!
http://bugteaser.blogspot.com
It would be an awfully good idea to point your readers towards http://www.context-driven-testing.com, and have them look there. Also, have a look at http://www.satisfice.com/blog/archives/74.
The point of context-driven testing is that it starts with considering the context, rather than merely acknowledging its importance after you've chosen some particular practice.
---Michael B.
Michael,
Yep! You're very much true. I have added the links in post for the readers.
I will keep your notes with for my future posts.
Best Regards,
Amit
testing is my passion!!!
http://bugteaser.blogspot.com
Context-Driven Testing has nothing to do with agile testing. It also has nothing to do with exploratory testing.
All it means is that you fit the testing to the nature of the testing problem. Solve the problem. That's it.
I was thinking the same, "how Context Driven Testing can be *arguably* called 'agile testing'?" Was writing to Bugteaser as I was eager to know what thoughts made to conclude that.
Context Driven Testing can shape the thoughts of tester into agile (agile here is not the same term used for 'Agile' process or methodology)thoughts if understood what it is.
Some of the techniques is being used in Context-Driven testing:
* Exploratory Testing
* GrayBox Testing
* Context Driven Testing approach does not highlights any practices or techniques or approaches, since it may or may not yield the very same result what was perceived earlier. Or this might not suit in all contexts.
* It starts to grow by analyzing the influencing system's specific or current context /for project context/, along with what is expected from the testing by the user who matters.
* Context Driven Testing never said or says that the Context Driven approach is the best. But any approaches and techniques can be tailored and used for their tasks contexts, if it suits and yields the value to the user.
It is glad to see that you are also learning. Learning are also prone to failures and errors. But they give learning yet again. Good thing is that, you have put your thoughts. These thoughts get strengthened when they are shared and interpreted.
I know for the fact when I will post this post it will have so many questions to be raised.
I am not an 'expert' and never refer to myself as an 'expert'. All my life I will be learning 'something or the other' through my thoughts whether they are rightly put in words or not.
I really liked you guys all jumped in (Michael, James Bach, Learning) and shared your thoughts on this to make it more fruitful.
Best Regards,
Amit
testing is my passion!!!
http://bugteaser.blogspot.com