E. Kit. Software Testing in the Real World. Addison-Wesley, Reading, MA, 1995. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
The Impact of Test Suite Granularity on the.. - Rothermel.. (2001) (3 citations) (Correct)
....cases may prevent test inputs that appear later in the test cases from exercising the requirements they are intended to exercise, by causing later inputs to be applied from system states other than those intended. In part, the foregoing examples involve test case size, a term used informally in [1, 2, 13, 15] to denote notions such as the number of commands applied to, or the amount of input processed by, the program under test, for a given test case. However, there is more than just test case size involved: when engineers increase or decrease the number of requirements covered by each test case, this ....
....begin locating and correcting faults earlier than might otherwise be possible. 2. 2 Related Work Many papers have examined the costs and bene ts of regression test selection, test case prioritization, and test case reduction [5, 6, 8, 14, 28, 32] Several textbooks and articles on testing [1, 2, 6, 11, 13, 15, 28] have discussed tradeo s involving test suite granularity. None of this literature, however, has formally examined tradeo s involving granularity, much less done so in relation to regression testing. In [27, 29] test suite granularity is speci cally treated as a factor in two studies of ....
E. Kit. Software Testing in the Real World. Addison-Wesley, Reading, MA, 1995.
The Impact of Test Suite Granularity on the.. - Rothermel.. (2002) (3 citations) (Correct)
....cases may prevent test inputs that appear later in the test cases from exercising the requirements they are intended to exercise, by causing later inputs to be applied from system states other than those intended. In part, the foregoing examples involve test case size, a term used informally in [1, 2, 13, 15] to denote notions such as the number of commands applied to, or the amount of input processed by, the program under test, for a given test case. However, there is more than just test case size involved: when engineers increase or decrease the number of requirements covered by each test case, this ....
....begin locating and correcting faults earlier than might otherwise be possible. 2. 2 Related Work Many papers have examined the costs and benefits of regression test selection, test case prioritization, and test case reduction [5, 6, 8, 14, 27, 31] Several textbooks and articles on testing [1, 2, 6, 11, 13, 15, 27] have discussed tradeoffs involving test suite granularity. None of these documents, however, has formally examined these tradeoffs, or done so in relation to regression testing. In [26, 28] test suite granularity is specifically considered as a factor in two studies of regression test ....
E. Kit. Software Testing in the Real World. Addison-Wesley, Reading, MA, 1995.
Identification of Test Cases from Business Requirements of.. - Jonathan Maletic Ph (Correct)
....tested products that have unpleasant surprises for customers (LaMonica, 1995) Testing is a central concept to the construction of quality software. The cost and quality benefits of conducting testing from the very initial phases of a software development project are well known and documented (Kit 1997). If there is an error in the requirements or the functional design of the system, the cost of fixing such an error at a late stage in development is immense compared to finding and fixing the error at an earlier phase (Pressman, 1997) An effective process in place for software testing will ....
....development is immense compared to finding and fixing the error at an earlier phase (Pressman, 1997) An effective process in place for software testing will resolve the dilemma of inadequately tested products. Software testing must be an integrated part of the entire software development process (Kit 1997). The Process Overview The methodology introduced refines information contained in the business requirement of a software system. The requirements are described as a set of functional requirements. In the general domain of information, business, or transaction processing these functional ....
Kit, Edward. Software Testing in the Real World, Addison-Wesley, 1997.
On Test Suite Composition and Cost-Effective.. - Rothermel, Elbaum.. (2003) (Correct)
No context found.
E. Kit. Software Testing in the Real World. Addison-Wesley, Reading, MA, 1995.
On Test Suite Composition and Cost-Effective.. - Rothermel, Elbaum.. (2003) (Correct)
No context found.
E. Kit. Software Testing in the Real World. Addison-Wesley, Reading, MA, 1995.
Increasing Understanding of the Modern Testing.. - Maaret Pyhjrvi Conformiq (Correct)
No context found.
Kit, E., Software Testing in the Real World, AddisonWesley, 1995.
Teaching Domain Testing: A Status Report - Kaner (2004) (Correct)
No context found.
Kit, E. Software Testing in the Real World, Addison-Wesley, 1995
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC