2012
DOI: 10.1002/9781119202486
|View full text |Cite
|
Sign up to set email alerts
|

The Art of Software Testing

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
5
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 231 publications
(8 citation statements)
references
References 0 publications
0
5
0
Order By: Relevance
“…The tests may be seen as a set of processes that are designed, developed and applied throughout the life of software development to detect and correct defects and faults found during and following the implementation of the code, and thus raise the quality and reliability of the program delivered to the end user [2]. However, applying thorough software tests that allow the testing of the software component in its entirety, as well as being both an expensive and timeconsuming task, is an almost impossible one.…”
Section: Introductionmentioning
confidence: 99%
“…The tests may be seen as a set of processes that are designed, developed and applied throughout the life of software development to detect and correct defects and faults found during and following the implementation of the code, and thus raise the quality and reliability of the program delivered to the end user [2]. However, applying thorough software tests that allow the testing of the software component in its entirety, as well as being both an expensive and timeconsuming task, is an almost impossible one.…”
Section: Introductionmentioning
confidence: 99%
“…The graph is traversed back from the effects to the causes and test cases are created according to specific decision rules (cf. [32] and [33]). These rules achieve the maximum probability of finding failures while avoiding the complexity of generating 2 n test cases, where is the number of causes.…”
Section: Fundamentalsmentioning
confidence: 99%
“…Subsequently, CiRA applies the BPST (cf. [32] and [33]) to derive the minimum number of required test cases from each CEG. Figure 6 presents an overview of the CEGs created by CiRA and the respective automatically generated test specifications for each causal requirement included in the THEMAS requirements specification (see Figure 1).…”
Section: Running Examplementioning
confidence: 99%
“…Over the past few decades, software testing has been the most widely used method for ensuring software quality [1]. The tests may be seen as a set of processes that are designed, developed and applied throughout the life of software development to detect and correct defects and faults found during and following the implementation of the code, and thus raise the quality and reliability of the program delivered to the end user [2]. However, applying thorough software tests that allow the testing of the software component in its entirety, as well as being both an expensive and timeconsuming task, is an almost impossible one.…”
Section: Introductionmentioning
confidence: 99%
“…Even trying to test the simplest software, a large number of test cases can be generated due to the many possible combinations of input parameters. Creating test cases for all these possibilities is an unfeasible and impractical process [1,2]. For example, if it is required to test a software component that receives as input parameters values from five sensors and each sensor can take 10 different values, 10 5 or 100,000 different test cases would then be required to exhaustively test that component.…”
Section: Introductionmentioning
confidence: 99%