000 03007nam a22003377a 4500
003 OSt
005 20250927102237.0
008 250927s20242024nyua|||er|||| 001 0 eng d
020 _a9781484298923 [paperback]
040 _aUniversity of Cebu-Banilad
_cUniversity of Cebu-Banilad
100 _aForgàcs, Istavàn,
_eauthor.
245 _aModern software testing techniques :
_ba practical guide for developers and testers /
_cIstavàn Forgàcs, Atilla Kovàcs.
260 _aNew York, NY :
_bApress,
_cc2024.
300 _axviii, 266 pages :
_billustrations (black and white) ;
_c23 cm.
336 _2rdacontent
_atext
337 _2rdamedia
_aunmediated
338 _2rdacarrier
_avolume
504 _aIncludes bibliographical reference and index.
505 _aChapter 1: Software testing basics -- Chapter 2: Test design automation by model-based testing -- Chapter 3: Domain testing -- Chapter 4: Developers and testers should constitute a successful team -- Chapter 5: Conclusion.
520 _a"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 morecomplex 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. " --Provided by the publisher
521 _aAdult
541 _aPurchased
_xOrtega, Eric
_yCollege of Computer Studies
_zComputer Studies : Information Technology
546 _aText in English
650 _aIT project management
650 _aSoftware project management
650 _aSoftware testing
700 _aKovàcs, Attila,
_eauthor.
942 _2ddc
_cBK
998 _cJanna [new]
_d09/27/2025
999 _c14461
_d14461