RETHINKING TEST DESIGN: REQUIREMENTS, ACCEPTANCE AND AUTOMATION

RETHINKING TEST DESIGN: REQUIREMENTS, ACCEPTANCE AND AUTOMATION
It seems that no matter how much time is spent on technology, the outcome of software development projects is still uncertain and today’s challenges seem to be the same now as they were thirty years ago. One could argue that it suits the IT service industry to be inefficient and unpredictable and that may be so. But what can business do to force IT to change? How can testers help their business stakeholders to get what they want out of IT?
In this brand-new workshop, software testing guru suggests that a change of thinking could improve the situation. At the heart of this thinking are some key

principles:
• Refocus on requirements (requirements as a driver of development, not an irrelevance, once developments start)
• Requirements are ‘for life’ (retained and managed for the life of a system, not just initial development)
• Requirements plus ‘examples of use’ define the need (requirements alone are never enough)
• Test and accept requirements, then test and accept the system
• We need automated support for requirements testing and acceptance test design (the valuable part), not just test execution (the easy part)
A new way of capturing requirement and test knowledge is required. This workshop explores how business stories and a Business Story Method can be used to test, improve and increase the value of requirements, provide the basis for consistent acceptance tests and form the basis of test automation at a business level.

Who Should Attend
This workshop is aimed at testers who want to improve their analysis skills, business analysts who want understand the challenge of testing and users who are responsible for communicating requirements.
Using a simple case study, delegates will get some first-hand practice in writing stories, scenarios and examples. We’ll use the Testela Business tool to capture some business stories, define business process paths, manage a requirements-test and generate skeletal acceptance tests. We’ll also use the tool to show how a Dictionary provides opportunities for better business impact analysis, regression testing, and interfaces to automated test tools.

You will learn
• A powerful technique for deriving stories from requirements
• How the disciplines of testing can be used to test requirements
• How the investment in requirements can be retained and reused for the lifetime of a system, not just the initial development
• How the language we use in writing requirements and stories influences how we understand and test
• How to use a software tool to support this process.

Contact : Vijay :cell;0-94400 89341

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License