Have Servers, will travel











Testing Master Class


Key Points

          How to calculate the cost of failure for your organization

          How to quantify the complexity of a multi-application system

          Why you should adopt a risk-based test strategy

          Automated test execution tools - some success stories 


Steps to select this Workshop:

1.Select the Venue and Dates here and then press: ADD TO CART.


Select Location and Date


2.Register for the Workshop by pressing this link Register




Failure is not an option

We all know that it costs loads of money if we test, and yet it potentially costs us even more if we donít test. However, trying to cope with todayís business and technical pressures with fewer resources means that there is never enough time to test it all to your complete satisfaction. How much does it cost your organization if your web-site is down for an hour, a day or even longer? This session provides some insights into the problems and shows you a practical way to calculate the cost of failure for your organization.


Determining system complexity

It is a fact of life that todayís IT systems are more complex than ever before. This complexity is unfortunately beating some test teams. This session shows you how to calculate complexity and thus determine the test effort. We start with a definition of complexity that can be applied to all issues that a test team may encounter when testing an enterprise-sized application. We then go on to define a methodology and tool to quantify the complexity of a multiple-application system including networks, system interfaces, and business process and demonstrate how this complexity factor can be used to compare differing applications and be used to estimate staffing and schedule.


Developing a risk-based test strategy

This session provides some insights into how you might structure your test processes to ensure valuable resources are used in the most effective way. How often do you run out of time or money on a testing project and yet still find loads of bugs once youíve gone live? Why is the test environment never ready in time for the testing despite all the promises? In this session, you will learn how to adopt a risk-based test strategy within your planning process. By involving all stakeholders in a project and assessing the risks to the business, your testing effort can focus on important areas of concern.


Why do my tools end up as shelf-ware?

We have all bought software testing tools only to find several months later that they didnít actually meet our requirements and solve the test managerís problem. There is still not enough time to do all of the testing and now the resources (automation experts) are costing even more than with a manual approach! This session provides focus on to the real reasons why companies fail to get value from test tools and discusses three case studies where tool benefits easily outweigh the costs of implementation.


Intended audience


Our series of special seminars that we call the "Testing Master Class" are aimed at senior testing professionals, senior consultants and managers from all IT disciplines who have an interest in saving money and being more efficient in their test approach. As well as learning from the seminar leaders, delegates will be expected to participate fully in the discussions and contribute their own views and ideas on key software testing issues. 


Seminar Leaders


The leaders of this Testing Master Class are Marquis Harding and Steve Allott and there will be a special guest speaker on the second day.


Marquis is the founder and CEO of Reality Test Inc. and has over 30 years experience in IT including considerable experience of testing large-scale complex systems at Microsoft Corporation.


Steve is a well-known and popular trainer and has over 25 years in the IT industry specializing in financial services and telecommunications and is now a principal consultant at ElectroMind, a company that creates and delivers innovative and value added training courses in software testing.




Top of Page


© 2001 Ė 2002Reality Testģ