| 000 | 03723nam a22004935i 4500 | ||
|---|---|---|---|
| 001 | 978-1-4842-9893-0 | ||
| 003 | DE-He213 | ||
| 005 | 20251030110859.0 | ||
| 007 | cr nn 008mamaa | ||
| 008 | 231227s2024 xxu| s |||| 0|eng d | ||
| 020 |
_a9781484298930 _9978-1-4842-9893-0 |
||
| 024 | 7 |
_a10.1007/978-1-4842-9893-0 _2doi |
|
| 050 | 4 | _aQA76.76.T48 | |
| 072 | 7 |
_aUMZT _2bicssc |
|
| 072 | 7 |
_aCOM051330 _2bisacsh |
|
| 072 | 7 |
_aUMZT _2thema |
|
| 100 | 1 |
_aForgács, István. _eauthor. _4aut _4http://id.loc.gov/vocabulary/relators/aut _968530 |
|
| 245 | 1 | 0 |
_aModern Software Testing Techniques _h[electronic resource] : _bA Practical Guide for Developers and Testers / _cby István Forgács, Attila Kovács. |
| 250 | _a1st ed. 2024. | ||
| 264 | 1 |
_aBerkeley, CA : _bApress : _bImprint: Apress, _c2024. |
|
| 300 |
_aXVIII, 266 p. 53 illus. _bonline resource. |
||
| 336 |
_atext _btxt _2rdacontent |
||
| 337 |
_acomputer _bc _2rdamedia |
||
| 338 |
_aonline resource _bcr _2rdacarrier |
||
| 347 |
_atext file _bPDF _2rda |
||
| 520 | _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. | ||
| 650 | 0 |
_aComputer programs _xTesting. _967452 |
|
| 650 | 0 |
_aSoftware engineering _xManagement. _967453 |
|
| 650 | 1 | 4 |
_aSoftware Testing. _967454 |
| 650 | 2 | 4 |
_aSoftware Management. _967455 |
| 700 | 1 |
_aKovács, Attila. _eauthor. _4aut _4http://id.loc.gov/vocabulary/relators/aut _968531 |
|
| 710 | 2 | _aSpringerLink (Online service) | |
| 773 | 0 | _tSpringer Nature eBook | |
| 776 | 0 | 8 |
_iPrinted edition: _z9781484298923 |
| 776 | 0 | 8 |
_iPrinted edition: _z9781484298947 |
| 776 | 0 | 8 |
_iPrinted edition: _z9798868807039 |
| 856 | 4 | 0 | _uhttps://doi.org/10.1007/978-1-4842-9893-0 |
| 912 | _aZDB-2-CWD | ||
| 912 | _aZDB-2-SXPC | ||
| 999 |
_c56893 _d56893 |
||