Posts Tagged ‘scripted testing’

Are there any passionate script testers? February 5, 2010 10 Comments

When looking for personel in general it is common that we want passionate people who love their work. Most passionate testers that I read about are usually part of the context-driven movement. Can there be testers out there that are really passionate about how they work in the heavy scripted test environment, where someone else [...]

Introducing exploratory testing in a scripted test environment November 18, 2009 5 Comments

In many organisations it is hard to change how you are working. You might be bound to certain CM tools, how things are expected to be planned, documentation systems, management expectations, project management expectations and so on. In many of these traditional environments you might also use the regular test plans, test matrices, test specifications, [...]

Exploratory Testing vs. Scripted Testing – rich terminology November 16, 2009 1 Comment

Exploratory Testing in its purest form is an approach that focus on learning, evolution and freedom.
Cem Kaner’s definition is to the point: “Exploratory software testing is a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test [...]

Scripted vs Exploratory testing from a managerial perspective July 30, 2009 5 Comments

From a managerial perspective without knowing too much about testing, your sole experience comes from the scripted test environment…
What does Scripted Testing include?

Control over what is to be tested, in the sense that you have a clear coverage of test cases on certain areas. Reports where you can see exactly how many test cases are [...]

Testing Clichés Part I – Expected Results March 23, 2009 3 Comments

Sometimes it is said that each test case must have an expected result, or even worse, that each step of a test case must have an expected result.
This is the extreme of scripted testing that I dislike for two reasons:
* It takes a lot of time to write and follow detailed test cases; time that [...]