In today’s economic climate there is increasing pressure to “do more with less”. Just what does this mean in the context of software testing? With this question in mind we will take a critical look at Risk Based testing, looking at key success factors, as well as common pitfalls. We will look first at the raw material for effective risk based testing, the Test Analyst.

Most of the literature produced about software testing focuses what we do. Very little thought seems to be given to who we are. But who we are defines how well we do whatever it is we do. What makes a good test analyst? Is it knowledge, skill, personality? Are there any fundamental defining characteristics of a good test analyst? With these questions in mind we have completed an And Map for test analysts. And Mapping is a method for differentiating between people; and then analysing the differences to determine major factors that influence a person’s effectiveness in their work. We’ll present the findings of the And Map process, highlighting the fundamental attributes of an effective test analyst.

Then we will look at Risk Based testing. Rather than look at how to complete risk based testing, a topic that is well covered in the literature, we’ll look at some common traps in a risk based testing programme and how to effectively manage the risks associated with risk based testing. From this basis I’ll outline a strategy for Risk Based Testing that we are finding effective.