03354nam a22004095i 4500001001800000003000900018005001700027007001500044008004100059020001800100024003500118050001600153072001700169072002300186072001600209100008200225245015300307250001800460264005400478300004600532336002600578337002600604338003600630347002400666520184400690650003202534650003802566650002202604650002502626700007902651710003402730773002602764776003602790776003602826776003602862856004602898978-1-4842-9893-0DE-He21320251030110859.0cr nn 008mamaa231227s2024    xxu|    s    |||| 0|eng d  a97814842989307 a10.1007/978-1-4842-9893-02doi 4aQA76.76.T48 7aUMZT2bicssc 7aCOM0513302bisacsh 7aUMZT2thema1 aForgács, István.eauthor.4aut4http://id.loc.gov/vocabulary/relators/aut10aModern Software Testing Techniquesh[electronic resource] :bA Practical Guide for Developers and Testers /cby István Forgács, Attila Kovács.  a1st ed. 2024. 1aBerkeley, CA :bApress :bImprint: Apress,c2024.  aXVIII, 266 p. 53 illus.bonline resource.  atextbtxt2rdacontent  acomputerbc2rdamedia  aonline resourcebcr2rdacarrier  atext filebPDF2rda  aMany 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 valueanalysis, 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. You will: Apply efficient test design techniques for detecting domain faults Work with modeling techniques that combine all the advantages of state transition testing and use case testing Grasp the two-phase model-based testing technique Use test design efficiently to find almost all the bugs in an application. 0aComputer programsxTesting. 0aSoftware engineeringxManagement.14aSoftware Testing.24aSoftware Management.1 aKovács, Attila.eauthor.4aut4http://id.loc.gov/vocabulary/relators/aut2 aSpringerLink (Online service)0 tSpringer Nature eBook08iPrinted edition:z978148429892308iPrinted edition:z978148429894708iPrinted edition:z979886880703940uhttps://doi.org/10.1007/978-1-4842-9893-0