<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Modern software testing techniques</title>
    <subTitle>a practical guide for developers and testers</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Forgàcs, Istavàn</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">author. </roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Kovàcs, Attila</namePart>
    <role>
      <roleTerm type="text">author. </roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">nyu</placeTerm>
    </place>
    <place>
      <placeTerm type="text">New York, NY</placeTerm>
    </place>
    <publisher>Apress</publisher>
    <dateIssued>c2024</dateIssued>
    <dateIssued encoding="marc">2024</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>xviii, 266 pages :  illustrations (black and white) ;  23 cm. </extent>
  </physicalDescription>
  <abstract>"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 </abstract>
  <tableOfContents>Chapter 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. </tableOfContents>
  <targetAudience>Adult </targetAudience>
  <targetAudience authority="marctarget">adult</targetAudience>
  <note type="statement of responsibility">Istavàn Forgàcs, Atilla Kovàcs.</note>
  <note>Includes bibliographical reference and index. </note>
  <note>Purchased  Ortega, Eric College of Computer Studies Computer Studies : Information Technology</note>
  <note>Text in English </note>
  <subject>
    <topic>IT project management</topic>
  </subject>
  <subject>
    <topic>Software project management</topic>
  </subject>
  <subject>
    <topic>Software testing</topic>
  </subject>
  <identifier type="isbn">9781484298923 [paperback]</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">University of Cebu-Banilad</recordContentSource>
    <recordCreationDate encoding="marc">250927</recordCreationDate>
    <recordChangeDate encoding="iso8601">20250927102237.0</recordChangeDate>
  </recordInfo>
</mods>
