The Seven Basic Principles of the Context-Driven School

http://www.context-driven-testing.com/

Some catches:

Context-oblivious testing is done without a thought for the match between testing practices and testing problems. This is common among testers who are just learning the craft, or are merely copying what they’ve seen other testers do.

Context-specific testing applies an approach that is optimized for a specific setting or problem, without room for adjustment in the event that the context changes. This is common in organizations with longstanding projects and teams, wherein the testers may not have worked in more than one organization. For example, one test group might develop expertise with military software, another group with games. In the specific situation, a context-specific tester and a context-driven tester might test their software in exactly the same way. However, the context-specific tester knows only how to work within her or his one development context (MilSpec) (or games), and s/he is not aware of the degree to which skilled testing will be different across contexts.

Agile development models advocate for a customer-responsive, waste-minimizing, humanistic approach to software development and so does context-driven testing. However, context-driven testing is not inherently part of the Agile development movement.

There are always constraints. Some of them are practical, others ethical. But within those constraints, we start from the project’s needs, not from our process preferences.

So here I am

So here I am. Somewhere in the middle of  Holland forced to change my expertise. The way ahead now looks as becoming a tester. An agile test engineer.

One starts with reading allot on the matter. And coming across a blog post from "http://www.passionatetester.com/" Dawn Cannan, and having read allot of other blogs on the matter, I decided to start a blog on my experience.

Where do I stand now concerning knowledge on agile testing ......while reading on it the last 3 weeks?
I realized that what I have been doing the last 5 years is all related to agile testing. I just missed the framework, the insight, the tools to give it the Agile touch. Talking to software engineers around me concluded the idea that agile testing was something we all do (or think in) in some kind of way.

TMap, XP, Scrum, Kanban, Waterfall, V model, it is all entering the floodlight. I am teased, eager to get my hands on these processes, believes, working methods. But first I need to get more details, experience, insights on the various outskirts on the matter.

I hope I can keep this blog filled with the stuff that keeps me busy in this new experience I am starting on.

Later ..........