Writing Good Test Requirements

1 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 51 vote, average: 5.00 out of 5
Please Log in or register to rate

Writing Good Test Requirements


Statistic show that most of the bugs in software applications derive from incomplete or inaccurate functional requirements.  Before new code is designed, it is crucial to finely revised and rewrite the requirements. Ambiguous and even just unclear requirements cause faulty code and expensive software products that do not deliver the intended vision and customer values.

Writing good requirements in general and test requirements in particular is a main element in reducing the cost of software. When the requirements are clear, the   product manager can clarify the needs of the customer and the developers can understand what the need to code. Poorly written requirements directly increase bug numbers and the probability for bugs in production.

Bugs elimination and early discovery is critical for high quality software the writing good test requirements is a key element in achieving it. In the workshop, testers will learn how to write good and even great Test Requirement


Target Audience:
Software quality engineers, testers, project managers and test managers.

Good grasp of software testing terminology, methods, techniques and processes.

Course Topics

Module 1 – Introduction

  • What are software requirements?
  • Engineering Requirements, functional vs. technical requirements
  • Impact of poor requirements

Module 2 – Requirements Management Development Process

  • Analysis, Specification & Validation
  • Change & Version control
  • Requirements status tracking

Module 3 – What are software test requirements?

  • Test requirements development process
  • How test requirements fit into the life cycle
  • How do Test Requirements relate to the Test Plan?
  • Fitting Test Requirements into the testing picture

Module 4 – How to recognize good and testable requirements?    

  • What will be your requirement satisfaction criteria?
  • Testing the clarity and consistency of the requirements
  • Checking if the requirements are related to the project goal
  • Finding poorly defined, missing or inadequate requirements
  • Validating requirements testability

Module 5 – Test requirements approaches

  • Verbs/actions
  • If.. When.. Then..
  • Writing requirements as Agile User Stories
  • Working with templates

Module 6 – How to write a Test Requirements?

  • Entrance Criteria for Business Requirements
  • Writing a clear functional test description
  • How to use ‘Definition of Done’ (DOD)
  • Exit Criteria for Test Requirements
  • Organizing Test Requirements

Module 7 – Labs

  • Exercise 1 – agile test requirements
  • Exercise 2 – creating test requirement templates
© Copyright - Skilit - Site by Dweb