Textbook in PDF format

Many books have been written about software testing, but most of them discuss the general framework of testing from a traditional perspective. Unfortunately, traditional test design techniques are often ineffective and unreliable for revealing the various kinds of faults that may occur. This book introduces three new software testing techniques: Two-Phase Model-Based Testing, the Action-State Testing, and the General Predicate Testing, all of which work best when applied with efficient fault revealing capabilities.
You’ll start with a short recap of software testing, focusing on why risk analysis is obligatory, how to classify bugs practically, and how fault-based testing can be used for improving test design. You’ll then see how action-state testing merges the benefits of state transition testing and use case testing into a unified approach. Moving on you’ll look at general predicate testing and how it serves as an extension of boundary value analysis, encompassing more complex predicates.
Two-phase model-based testing represents an advanced approach where the model does not necessarily need to be machine-readable; human readability suffices. The first phase involves a high-level model from which abstract tests are generated. Upon manual execution of these tests, the test code is generated. Rather than calculating output values, they are merely checked for conformity. The last part of this book contains a chapter on how developers and testers can help each other and work as a collaborative team.
The origin of most software bugs can be attributed to the requirements phase. Therefore, the most effective approach to reducing the number of newly discovered bugs in a project is to incorporate a requirements analysis stage that teams must undertake prior to commencing coding. Any requirements engineering handbook explains to you why completeness, clearness, correctness, consistency, and measurability are key attributes in defining and checking the right requirements. The granularity of requirements determines the extent to which the requirements capture the desired functionality, behavior, data, and other characteristics of the system being developed. Requirements may vary in granularity, ranging from high-level abstract statements to more detailed and specific descriptions. The granularity depends on the nature of the project, the needs of stakeholders, and the development methodology being followed.
What You'll Learn:
Apply efficient test design techniques for detecting domain faults
Work with modeling techniques that combine all the advantages of state transition testing and uses case testing
Grasp the two-phase model-based testing technique
Use test design efficiently to find almost all the bugs in an application
Who This Book Is For:
Software developers, QA engineers, and, business analysts