Exploratory Testing Explained

Lee Copeland

Software Quality Engineering

Exploratory testing is testing technique that emphasizes the freedom and responsibility of the tester to continually optimize the value of his work. It is the process of three mutually supportive activities performed simultaneously—learning, test design, and test execution. The tester designs and executes tests while exploring the product. With skill and practice, exploratory testers typically uncover considerably more defects than when the same amount of effort is spent in scripted testing. In exploratory testing, the tester controls the design of test cases as they are performed rather than days, weeks, or even months before. In addition, the information the tester gains from executing a set of tests then guides him in designing and executing the next set of tests. Lee Copeland describes specific heuristics and techniques of exploratory testing to help you get the most from this highly productive approach.

How good is your testing? Check it out with TMMi

Clive Bates


How do you know whether the testing in your organisation is good enough for the applications you test? How do you really know what is working well and what you need to do to get even better?

In this tutorial Clive will look at why organisations firstly need to consider improving the testing they do across the whole lifecycle whether they use the more traditional V-model or Agile approaches. Secondly, before undertaking any improvements how do you understand exactly what the current state of your organisation’s testing processes are? To help you with that understanding it is important to gauge your organisation against an internationally recognised model. TMMi is the most independent testing focused model that will give you the detailed understanding and knowledge about where you are now against specific maturity levels. The result of a TMMi assessment will ensure you have a clear understanding of your organisations current strengths, and just as important what areas you need to focus on improving.

In the tutorial Clive will take you through the model in enough detail to help you consider where your organisation could be against TMMi, and how to score yourselves supported by appropriate exercises. You will then be able to have a view of your own organisations maturity.

Should I weigh or should I go – do’s and don’ts about metrics

Olivier Denoo


This half-day tutorial is targeting a broad audience of testers and test managers (whatever their former experience with projects and metrics). It is pinpointing, in a humorous way, lots of common (mis) behaviors and issues that the Test Management community has to face regarding the evaluation and measurement of the test process.

By attending this tutorial, you’ll see how metrics can be organized within a structured framework starting from requirements to defects, with a serious twist of progress and performance measurements. You will also discover how sometimes so-called obvious metrics can be misleading (and lead to wrong conclusions or lead to make wrong decisions) or misused (by management or testers). Whatever, there’s no hope without metrics as they are essential for us to know and understand what is going on (another good reason to choose and implement the right ones in a right way). Last but not least, this tutorial is totally tool-independent – it’s not about tool at all, but about strategy and methodology and return of experience in the wide.

Practical Risk-based Testing

Erik van Veenendaal

Improve IT Services BV,

Although most projects implicitly use some kind of risk-based approach for prioritizing testing activities, critical testing decisions should be based on a thorough product risk assessment process with key business drivers as the foundation. PRISMA (PRoduct RISk MAnagement), a practical method for performing systematic product risk assessments is presented. It is explained how to carry out risk identification and enalyzes, and how to use the outcome to select the best test approach. Learn how to use PRISMA in both traditional and agile projects, including creating an agile sprint test plan. Practical experiences are shared, problems overcome and results observed employing product risk assessments. Learn how to optimize your test effort by including product risk assessment in your testing practices. Develop a rigorous approach to inform project stakeholders about important testing decisions and provide clear visibility on product risk status.

Load & Performance – Practical Principles

Yaron Tsubery

Enghouse Interactive

Load & performance, belong to the top ten list of most freighting words in software development especially when it comes to the point of sale of your product at times of extremely competitive market. One word that is really frightening is the word … STRESS (doesn’t it give you the shivers just hearing it?). This tutorial will get you acquainted with the terms in subject and will donate to your understanding of the whole desired process stages from Sales meetings through Design and architecture, Ways of implementation, Testing aspects and finally presenting results and reports. A part of the process you’ll be advised about ways to be aligned with your customer’s expectations, means that you’ll need to know and control the required lingo of the load profession, whether you’re sales person, developer or test engineer (e.g. ‘usage & traffic model’, ‘throughput’ etc’). You’ll be exposed to design and architecture solutions among with special guidelines for code writing and implementation. The load test engineers will understand better what the required information to initiate load & performance is; what to search for and how to improve their testing coverage, how & what to report and present in order to give an added value to those who make the decisions.
This practice is focused on projects of complex systems, delivered to telecommunication companies under restricted rules and stiff exit criteria elements, among tense delivery timelines.

Using Scrum Methods as a Test Manager

Klaus Olsen


This tutorial will learn you how to apply methods from SCRUM when you work as a Test Manager. Especially if you are not working in a SCRUM team or an Agile project, there will be more to learn, but members of Agile development team can also participate.

We will cover how Stand-Up meetings are very useful for you as a Test Manager, to stay on top of everything which is going on within your team. How you can use Burndown charters to communicate progress, and how Poker Planning Cards are very useful when you need to estimated the amount of work you have within your team.

The tutorial will also cover techniques to prioritise the task to cover as part of your Test Management, using a Backlog as another artefact from SCRUM.