Writing Good Test Requirements
A practical workshop in improving test design & adding business value
This workshop has been designed to assist participants in understanding better, 'what are test requirements?', “How to write test requirements?”, “How and when should we use them?”, “Why should we check their testability (and how)?”, and “For what purpose (what are the benefits)?” We shall also discuss the pros and cons of using test requirements.
In order to exercise test requirements, we will first discuss requirements engineering aspects, and identify the common fit palls that may be found in requirements - which might make them untestable.
The problem of poor requirements is well known: poorly defined requirements lead to poor quality products and a high cost of rework with the testers often being blamed for not doing enough testing! According to industry experts such as DeMarco and Boehm, poor requirements might consume as much as 75% of overall rework costs.
The solution is also well known: early involvement by testers in the requirements process, higher responsibility and involvement by product marketing/management and a lot more involvement by development. In this workshop we shall also experience writing test requirements from a specification document.
Writing test requirements is a step on the way to writing good requirements (as good feedback leads to improvement), it is related to as the Verification phase in the development of requirements process.
In the workshop, hints and tips will be suggested as to how to develop and recognize good, testable requirements, how to develop good test requirements and how to organize the test requirements in efficient hierarchy.
Software quality engineers, testers, developers, product engineers and product managers, project managers & test leaders who have good understanding of software testing principles, yet are still struggling with software quality issues due to poorly defined, missing or inadequate requirements, and/or which are lacking a test requirements phase in their test design process, and would like to improve it.
Professionals who seek ways to improve their test design, getting the test team closer to the business, and enable easier test case writing, while improving the requirements.
- Understand the requirements development process
- Understand the requirements management process
- Understand what software test requirements are
- Discuss how to create test requirements
- Understand where test requirements creation fits into the life cycle
- Recognize good, testable requirements
- Know what to look for when reviewing requirements specifications
- Appreciate the skills required by test requirements analysts
- Understand how to analyze and decompose requirement documents into test requirements
- Understand the impact of exercising Test Requirements process on the testing project
- This is an introduction to Software Test Requirements and does not cover requirements development and requirements management other than in broad terms
- This workshop is NOT an introductory course on software testing and participants must have a good grasp of software testing terminology and processes
- Participants will be expected to do some preparation by listing some ambiguous and ill-defined requirements from their current projects and be prepared to discuss these in the workshop in small groups
Mr. Alon Linetzki - is an expert test engineer, testing coach and a testing consultant with over 23 years in testing, and over 33 years in IT. During his career, Mr. Linetzki have participated and managed various types of development projects and testing projects with a large range of technologies, size and sector domain orientation from telecommunication and finance, to banking and embedded systems.
He is the author of multiple testing classes, including: Testing in an Agile Environment, ISTQB® Agile Tester, Exploratory Testing, Measurements and Metrics for Making Good Quality Decisions, Test Process Improvement Using TPI®, Risk Based Testing, Writing Good Test Requirements, and Test Automation for Decision Makers, Introduction to Test Automation, Personal Communication and presentation Skills, Root Cause analysis in Testing and Adding business value increasing ROI in testing, and more.
Mr. Linetzki is a popular speaker in international testing conferences since 1995. He is the co-founder of the Israeli Testing Certification Board (www.itcb.org.il), and the founder and chair of SIGiST Israel (www.sigist.org.il). He is leading the ISTQB® Partner Program worldwide as part of the marketing working group. He is also one of the authors of the new ISTQB® Foundation Level Agile Tester Certification, and is involved in the next level certification of ISTQB® Advanced Level – Agile Technical Tester. Mr. Linetzki is also the ISTQB® Marketing Chair (March 2016).
- What are software requirements?
- Software requirements
- Levels and types of requirements
- Requirements engineering
- Impact of poor requirements
- Impact of SDLC models
Requirements Development Process
Requirements Management overview
- Change control
- Version control
- Requirements status tracking
- Requirements tracing
Developing Good Requirements
- Individual requirements attributes
- Terms to avoid
- Common system requirements problems
- Requirements documents
- Writing guidelines
What are software test requirements?
- Background & Introduction
- Test requirements approaches
- Exercise: writing simple test requirements (ATM)
- Test requirements technique - If..When..Then..
- Optional Parameters
- Writing a test rule - checklist
- How test requirements fit into the life cycle?
- Test requirements development process
- Test Rules sources
- Decomposing Test Rules – Bonus exercise
The test requirements different dimensions
- Test rules dimensions & test requirements impact analysis
- Test rules classification & organization
Fitting test requirements to the TRH
- Review test hierarchy tree
- Discuss optimization tips for building the TRH
Essential skills of the test requirements analyst
- Identify and discuss Test requirements analyst skills
The impact of exercising TRs on the testing project
- TRs economics
- Utilizing resources
- Creating test cases
- Reviews with development
- Productivity, effectiveness and efficiency
- TRs economics
- Summary: Pros and Cons on test requirements