B. Beizer. Black-Box Testing. John Wiley and Sons, New York, NY, 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....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 ....

B. Beizer. Black-Box Testing. John Wiley and Sons, New York, NY, 1995.

....the original software in the first place, and thus are expensive. While in most cases testing of normal functionality is seen as necessary, there is a problem in that exception handling code and other portions of the system can overshadow the basic functionality in terms of testing complexity [5]. This means that in all but the most extreme safety critical cases, limited time, budget, and manpower often result in testing effort being concentrated on normal functionality, giving short shrift to dependability aspects. In other words, reliability testing can fall victim to the problems of ....

....detect whether a check for invalid data is missing from the program altogether. Additionally, structural testing typically requires access to source code, which may be unavailable when using COTS software components. A complementary approach is black box testing, also called behavioral testing [5]. Black box testing techniques are designed to demonstrate correct response to various input values regardless of the software implementation, and seem more appropriate for robustness testing. Two types of black box testing are particularly useful as starting points for robustness testing: domain ....

[Article contains additional citation context not shown here]

Beizer, B., Black Box Testing, New York: Wiley, 1995.

....in time are collected in form of time stamps that can be evaluated during or after the test run. We explain all extensions to TTCN 3 necessary to support the collection and evaluation of time stamps and show the applicability of our approach by means of an example. Motivation Testing (e.g. [1, 6, 7]) is an important issue during the development processes of communication systems and can be divided into two categories: testing of functional and non functional requirements. An important sub category of nonfunctional requirements are hard real time requirements [2, 8] Functional testing is ....

B. Beizer. Black-Box Testing. Wiley, 1995.

....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 ....

B. Beizer. Black-Box Testing. John Wiley and Sons, New York, NY, 1995.

....is tested has nothing to do with its internal structure, such tests must have been black box tests. In order to do them, the developer needs both: ffl A specification indicating at least the most critical values it has to be tested against. These values will result from domain partitioning [17, 2] ffl The test suite used during testing for arriving at this conclusion. To include both items with the code of the component into the repository seems not to require any additional effort on the developer s side. 3.5.2 Development With Reuse For the requester, we assume that he developed ....

B. Beizer. Black-Box Testing. John Wiley & Sons, Inc., New York, N.Y., 1995.

....based on some notion of fairness, or very concretely, based on some notion of real time triggering. The basic transition system model is very simple and easy to explain. Besides that, it has other advantages, such as: It fits in with traditional finite state black box testing techniques [1]. It can be used to unify the concepts of callable operation and autonomous transition, leading to a uniform treatment of both. It helps in suppressing control bias in specifications by the absence of loci of control . 10 H.B.M. Jonkers The only problem is that the basic transition ....

Beizer, B., Black-Box Testing, Wiley & Sons (1995).

....rapture, a fully implemented, domain independent, heuristic algorithm for solving this problem. Wrapper verification involves determining whether a wrapper correctly processes a given page. Our approach is an extension to the standard software engineering regression testing paradigm (e.g. [Beizer 1995]) we give the wrapper to be verified a known input page, and then check whether the output matches 4 Nicholas Kushmerick, Wrapper verification the expected correct output. We call the simplest such regression tester exact match. To verify a wrapper, exact match invokes it on the page returned ....

....this empirical distribution. The normality assumption is satisfied quite well in some cases (a b) and quite poorly in others (c d) 6 DISCUSSION Related work. rapture is based on the standard regression testing paradigm widely used in the software engineering and testing communities (e.g. [Beizer 1995]) However, wrapper verification is more difficult than standard regression testing, because of two moving targets: both the formatting regularities on which wrappers rely, and the underlying content, can change. While specialized programming languages for hand coding wrappers [Hammer et al. ....

Beizer, B. (1995), Black-Box Testing , John Wiley & Sons.

....executed by a test suite, but may not detect if such code is missing altogether. Additionally, structural testing typically requires access to source code, which is often unavailable when using COTS software components. An alternative approach is black box testing, also called behavioral testing [11]. This type of testing ignores the internal operation of the system being tested and instead focuses on whether the system produces the correct response to various input values. This is appropriate for testing COTS software since source code is often unavailable. Finally, blackbox testing enables ....

Beizer, B., Black Box Testing, New York: John Wiley, 1995.

....is the degree to which it functions correctly in the presence of exceptional inputs or stressful environmental conditions. 2] In some mature test suites so called dirty tests that measure responses to invalid conditions can outnumber tests for correct conditions by a ratio of 4:1 or 5:1. [3] The focus of this paper is the Ballista methodology for automatic creation and execution of a portion of these numerous invalid input robustness tests in particular tests designed to detect crashes and hangs caused by invalid inputs to function calls. The results presented indicate that ....

....executed by a test suite, but may not detect if such a test is missing altogether. Additionally, structural testing typically requires access to source code, which may be unavailable when using COTS software components. A complementary approach is black box testing, also called behavioral testing. [3] Black box testing techniques are designed to demonstrate correct response to various input values regardless of the software implementation, and seem more appropriate for robustness testing. Two types of black box testing are particularly useful as starting points for robustness testing: domain ....

Beizer, B., Black Box Testing, New York: Wiley, 1995.

....demonstrate that the software is operationally useful. Therefore, dynamic testing techniques will still be needed, even though static testing techniques are becoming more widely used. Dynamic testing techniques are generally divided into the two categories of black box and white box testing (Beizer, 1995; Sommerville, 1996) which correspond with two different software testing starting points: the internal structure of the software and the requirements specification. Basili and Selby (1987) conducted an experiment to compare the effectiveness of black and white box testing. The results of this ....

Beizer, B. (1995) Black--Box Testing (John Wiley & Sons, New York).

....black box testing techniques are most appropriate. We implement black box functional evaluation testing by employing boundary value analysis and equivalence partitioning techniques [18] While this is not the only test case design strategy available (or even necessarily the most effective [3]) it shows promise of being able to uncover many errors at a reasonable cost, where cost is the number of test runs per error discovered. In general, this type of black box testing involves the generation of a black box testset, the application of this testset to generate both correct ....

Beizer, B. Black-Box Testing. John Wiley & Sons, 1995.

....verification problem, and present rapture, a fullyimplemented, domain independent, heuristic algorithm for solving this problem. Wrapper verification involves determining whether a wrapper correctly processes a given page. Our approach is based on the black box or regression testing paradigm (e.g. (Beizer 1995)) we give the wrapper a page for which the correct output is known, and check that the wrapper in fact generates this output. The simplest such regression tester is strawman. To verify a wrapper, strawman invokes it on the page returned in response to a given query, and also on an earlier page ....

....problem, and presented rapture, a fully implemented, domain independent, heuristic solution. Verification is difficult because at many Internet sites, both the formatting regularities used by wrappers, and the underlying content, can change. Standard regression testing approaches (e.g. see (Beizer 1995)) are inapplicable, as they assume the underlying content is static. rapture uses a set of syntactic features to compute the similarity between a wrapper s output and the output for pages for which the wrapper is known to be correct. rapture combines the similarities to derive an overall ....

Beizer, B. 1995. Black-Box Testing. John Wiley & Sons.

....demonstrate that the software is operationally useful. Therefore, dynamic testing techniques will still be needed, even though static testing techniques are becoming more widely used. Dynamic testing techniques are generally divided into the two categories of black box and white box testing (Beizer, 1995; Sommerville, 1996) which correspond with two different software testing starting points: the internal structure of the software and the requirements specification. Basili and Selby (1987) conducted an experiment to compare the effectiveness of black and white box testing. The results of this ....

Beizer, B. (1995) Black--Box Testing (John Wiley & Sons, New York).

....Developing reliable and fault tolerant software is difficult and requires discipline both in specifying system functionality and in implementing systems correctly. Approaches for developing highly reliable software include the use of formal methods [11, 14, 9] and rigorous testing methods [2, 7, 13]. Testing cannot guarantee that software is correct [17] and verification requires enormous human effort and is subject to errors [6] Automated support is necessary to help ensure software correctness and fault tolerance. Fault injection has been proposed for use in mutation testing primarily ....

B. Beizer. Black-Box Testing. John Wiley & Sons, 1995.

No context found.

B. Beizer. Black-Box Testing. John Wiley and Sons, New York, NY, 1995.

No context found.

B.Beizer, Black-Box Testing. John Wiley & Sons, Inc, 1995.

No context found.

Beizer, B., 1995. Black-Box Testing. John Wiley & Sons, Inc.

No context found.

B.Beizer, Black-Box Testing. John Wiley & Sons, Inc, 1995.

No context found.

B. Beizer. Black-Box Testing. John Wiley and Sons, New York, NY, 1995.

No context found.

B. Beizer. Black-box testing. John-Wiley, 1995.

No context found.

Beizer, B. Black-Box Testing, John Wiley & Sons, 1995

No context found.

Beizer, B., Black Box Testing, New York:

No context found.

Beizer, B., Black Box Testing, New York: Wiley, 1995

No context found.

Beizer, B., Black Box Testing, New York: Wiley, 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