The first aim of this book is to provide a brief introduction to the discipline called testing. Quite a lot of the information and training on testing is technical, bureaucratic, complicated or... More > dated. This Pocketbook presents a set of Test Axioms that will help you determine what your testing mission should be and how to gain commitment and understanding from your management. The technical stuff might then make more sense to you.
The second aim of this Pocketbook is to provide a handy reference, an aide memoire or prompter for testing practitioners. But it isn’t a pocket dictionary or summary of procedures, techniques or processes. When you are stuck for what to do next, or believe there’s something wrong in your own or someone else’s testing or you want to understand their testing or improve it, this Pocketbook might be of help. It will prompt you to ask some germane questions of yourself, your team, your management, stakeholder or supplier.< Less
Business Stories are simple, compact ‘examples’ of the behaviour of software. When placed at the centre of software delivery, these stories close the communication gap between users,... More > developers and testers.
This pocketbook describes an approach to building software that uses Business Stories to enable project participants to communicate in natural language:
* Business analysts derive Business Stories from requirements to confirm with stakeholders that requirements can be trusted.
* Developers take the same stories and use them to help design their code and automatically test it.
* Test analysts take the same stories and add detail required for system and acceptance testing as software becomes available.
Written for business analysts, developers, testers and their managers, this pocketbook describes the core practices you need to manage requirements knowledge and deliver valuable software that works the way users want it, in a more reliable way.< Less