Beizer, B., Software Testing Techniques, 2nd. Ed. Van Nostrand Reinhold. 1990 Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Improving Software Quality Through Extreme Coverage With Jblanket - Agustin (2003) (Correct)
..... 100 C.32 Test LOC Tutor . 100 xii Introduction Software testing is a crucial element of Software Engineering. Testing can account for approximately half of the labor required to produce a working product [1]. Without proper planning and effective tests, development costs can increase dramatically during software development as unexpected failures emerge. In many cases, removing the errors that caused the failures, or bugs, becomes the single largest cost in software development [1] Error removal ....
....a working product [1] Without proper planning and effective tests, development costs can increase dramatically during software development as unexpected failures emerge. In many cases, removing the errors that caused the failures, or bugs, becomes the single largest cost in software development [1]. Error removal requires detection, correction, tests designed to detect them, and the execution of those tests. A common lesson Computer Science students learn at the beginning of their college careers is that the longer a bug remains undiscovered, the costlier it is to fix. In other words, as ....
[Article contains additional citation context not shown here]
Boris Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, second edition, 1990.
Hardware-Software Covalidation: Fault Models and Test Generation - Harris (Correct)
....to describe the relevant features of most covalidation fault models. 2.1 Textual Fault Models A textual fault model is one which is applied directly to the original textual behavioral description. The simplest textual fault model is the statement coverage metric introduced in software testing [3] which associates a potential fault with each line of code, and requires that each statement in the description be executed during testing. This model is very efficient since the number of potential faults is equal to the number of lines of code. On the other hand, it is well accepted 1 ....
....to describe a large set of design defects. 2.2 Control Dataflow Fault Models A number of covalidation fault models are based on the traversal of paths through the CDFG representing to the system behavior. The earliest control dataflow fault models include branch coverage and path coverage [3] models used in software testing. The branch coverage metric associates potential faults with each direction of each conditional in the CDFG. Branch coverage requires that the set of all CDFG paths covered during covalidation include both directions of all binaryvalued conditionals. Branch ....
[Article contains additional citation context not shown here]
B. Beizer, Software Testing Techniques, Second Edition, Van Nostrand Reinhold, 1990.
Model Checking for the Concurrent Constraint Paradigm - Garcia (Correct)
....many times the veri ed system is not the program code itself but some abstraction of it. Therefore, we cannot immediately ensure the correctness of the veri cation but it is also necessary to verify the correctness of the abstraction or simpli cation. 6. 2 Testing Testing (see [Mye79, Bei90, KFN93, Pat00] is a veri cation method which consists in executing the program that we want to verify and analyzing the executions (patterns) to detect errors. Each pattern is compared with the expected result and if they do not coincide, then an error is signed. This technique is based on the ....
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, USA, Second edition, 1990.
JBlanket: Support for Extreme Coverage in Java Unit Testing - Agustin (Correct)
....techniques are derived from the specifications and then applied [6] To ensure that intimate association with a module does not influence testing, this task is usually performed by person(s) other than the programmer. In the case of unit testing, the programmer and the tester is the same person [7]. However, in the case where the software development model used is Extreme Programming (XP) the programmer first designs the unit tests from the specifications before any code is implemented. It is only after some code is written that it can be exercised by the unit tests. One hundred percent ....
....that measures the amount of code that is exercised by the test cases. Boris Beizer claims that during unit testing 100 coverage is necessary, and that this level of coverage usually drops as modules are combined or as testing is done on huge systems of approximately 10 million lines of code [7]. On the other hand, Brian Marick conducted a study where he examined the different granularities of coverage, which will be discussed further in Section 2 [12] From his study, he claimed that 100 of feasible coverage is an acceptable level of coverage to achieve. 2 Of the different coverage ....
Beizer, Boris. Software Testing Techniques, second edition, Van Nostrand Reinhold, New York, 1990.
VOCAL: A Framework For Test Identification Deployment - Duncan Pemberton And (Correct)
....associated view of quality that we use the terms verification and validation for the process rather than testing to indicate the wide life cycle view of defect detection. Such a process is more than applying some form of test data selection technique like white, or black box testing [1, 34] to achieve a specific level of code (white box) or requirements (black box) coverage. The process actively involves system users. The final point to make is the importance of structured quality checks throughout development. Technologies like the Internet introduce many non functional ....
BEIZER, B.: "Software Testing Techniques" (Van Nostrand Reinhold, 1990) 2 edn.
Test Coverage Analyzer for Java - N. (2003) (Correct)
.... becomes an expensive phase which approximately requires 50 of the total e ort[19] Software testing and quality costs for manufactured items can be as low as 2 in consumer products or as high as 80 in products such as space ships, nuclear reactors and aircraft, where failure threatens life[3]. Success of testing depends on the test cases that are chosen. We should choose those test cases which cause failures. Several heuristics and methods have been proposed to choose the fault revealing test cases. All the heuristics can be broadly divided into two categories: Black box testing ....
Boris Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
Macro and Micro Perspectives on Strategic Software Quality.. - Xie, Notkin (2002) (4 citations) (Correct)
....coverage, e.g. function coverage or statement coverage, etc. 4. TEST CASE PRIORITIZATION BASED ON BOUNDARY VALUE COVERAGE Since a large number of faults tend to occur at boundaries of the input domain, testing boundary values has been extensively discussed in software testing handbooks [21][2][3] Most past research work in boundary value coverage has generally focused on test case generation instead of test case assessment, which can be used in regression testing, e.g. test case selection or test case prioritization, due in part to lack of tool support to collect boundary value ....
B. Beizer, Software Testing Techniques, 2 nd edition, Van Nostrand Reinhold, New York, USA.
Modeling the Cost-Benefits Tradeoffs for Regression.. - Malishevsky.. (2002) (Correct)
....overall cost of software [11, 17] Regression testing is an important part of maintenance, performed when software is modified to help ensure that it has not lost required functionality. Because regression testing is performed frequently, it can account for a large proportion of maintenance costs [1, 10, 17]. To reduce the cost of regression testing, engineers often save their test suites for use in retesting that software. As the software evolves, they add tests to these suites. As a result, the costs of maintaining and using the test suites increase. Several techniques have been devised for ....
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, 1990.
Automated Software Testing Using a Metaheuristic Technique.. - Diaz, Tuya, Blanco (2003) (Correct)
No context found.
Beizer, B., Software Testing Techniques, 2nd. Ed. Van Nostrand Reinhold. 1990
Infrastructure Support for Controlled Experimentation - With Software Testing (Correct)
No context found.
B. Beizer. Software Testing Techniques.VanNostrand Reinhold, New York, NY, 1990.
Modeling the Cost-Benefits Tradeoffs for Regression.. - Alexey Malishevsky And (2002) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, 1990.
Testability in Co-design Environments - Cotest Report On (Correct)
No context found.
B. Beizer, "Software Testing Techniques", (2nd ed.), Van Nostrand Rheinold, New York, 1990
High-Level Test Generation and Built-In . . . - Jervan (2002) (Correct)
No context found.
B. Beizer, "Software Testing Techniques," (2 nd edition), Van Nostrand Reinhold, 1990.
High-Level and Hierarchical Test Sequence Generation - Jervan, Peng, Goloubeva.. (2002) (Correct)
No context found.
Beizer B., "Software Testing Techniques", (2nd ed.). Van Nostrand Rheinold, New York, 1990.
Proceedings - Of The Naccq (Correct)
No context found.
Beizer (1992). Software testing techniques, Van Nostrand Reinhold, 1992.
Original Article - Berry Daudjee Dong (Correct)
No context found.
Beizer B (1990) Software testing techniques, 2nd edn. International Thomson Computer Press, London
Comparing Bug Finding Tools with Reviews and Tests - Wagner, Jürjens, Koller.. (2005) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Thomson Learning, 2nd edition, 1990.
Metamorphic Testing and Beyond - Chen, Kuo, Tse, Zhou (2004) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
Towards the Application of Classification Techniques to.. - Cheng, Cheung, Tse (2004) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
Automatic goal-oriented classification of failure behaviors.. - Chan, Cheng, Tse (2005) (Correct)
No context found.
Beizer, B., 1990. Software Testing Techniques, Van Nostrand Reinhold, New York.
Metamorphic Testing and its Applications - Zhou, Huang, Tse, Yang, Huang.. (2004) (Correct)
No context found.
Beizer, B. Software Testing Techniques, Van Nostrand Reinhold, New York, 1990.
Towards a Model for Automated Fault Localization in - Vhdl Designs Exploring (Correct)
No context found.
Boris Beizer, Software Testing Techniques, Van Nostrand Reinhold, 1990.
Input Generation for Path Coverage in Software Testing - Jos Costa Jccc (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Rheinhold, New York, second edition, 1990.
Selecting an Efficient OO Integration Testing Strategy.. - Le Hanh, Akif, Le Traon (2001) (Correct)
No context found.
# B. Beizer, "Software testing techniques," Van Norstrand Reinhold, 1990. ISBN 0-44220672 -0.
Testing Polymorphic Relationships - Alexander, Offutt (2003) (Correct)
No context found.
Boris Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, New York, 2nd edition, 1990.
Verifying Time Partitioning in the DEOS Scheduling Kernel - Penix, Visser, Park, al. (2004) (Correct)
No context found.
B. Beizer. Software Testing Techniques. 2nd ed, Van Nostrand Reinhold, New York, 1990.
Deductive Runtime Certification - Arkoudas, Rinard (2004) (Correct)
No context found.
B. Beizer. Software testing techniques. Van Nostrand Reinhold Co., New York, NY, 1990.
Metamorphic Testing and Beyond - Chen, Kuo, Tse, Zhou (2004) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
TRIPWIRE: Mediating Software Self-Awareness - Bowring, Rehg, Harrold (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
A Study of the Impact of Implementation Quality on Regression.. - Bowring (2001) (Correct)
No context found.
Boris Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 2nd edition, 1990.
Generic Program Monitoring by Trace Analysis - Jahier, al. (2002) (2 citations) (Correct)
No context found.
B. Beizer. Software testing techniques, volume 2nd ed. Int. Thomson Computer Press, 1990.
UML-CASTING: Test synthesis from UML models using constraint - Resolution Lionel Van (2003) (Correct)
No context found.
B. Beizer. Software Testing Techniques, Van Nostrand Reinhold, New York, 2nd ed., 1990.
Testing of Object-Oriented Programming Systems (Oops): A.. - Hayes (1994) (Correct)
No context found.
Beizer, Boris. Software Testing Techniques . Second Edition. New York, Van Nostrand Reinhold, 1990.
Test Coverage Analysis: A Method for Generic Reporting - Khan (1998) (1 citation) (Correct)
No context found.
Boris Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, second edition, 1990.
Security testing of SIP implementations - Wieser, Laakso, Schulzrinne (2003) (Correct)
No context found.
B. Beizer, Software Testing Techniques, 2nd ed., 1990.
Heuristics for Model Checking Java Programs - Groce, Visser (2002) (7 citations) (Correct)
No context found.
B. Beizer. Software Testing Techniques. 2nd ed., Van Nostrand Reinhold, New York, 1990.
Infrastructure Support for Controlled Experimentation with .. - Do, Elbaum, Rothermel (2004) (1 citation) (Correct)
No context found.
B. Beizer. Software Testing Techniques.VanNostrand Reinhold, New York, NY, 1990.
Understanding Data Dependences in the Presence of Pointers - Orso, Sinha, Harrold (2003) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, 1990.
Towards the Application of Classification Techniques to.. - Cheng, Cheung, Tse (2004) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 1990.
Infrastructure Support for Controlled Experimentation with.. - Do, Rothermel, al. (2004) (1 citation) (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, NY, 1990.
Variable Search Space For Software Testing - Ramn Sagarna Jose (2003) (Correct)
No context found.
B. Beizer, Software Testing Techniques, Van Nostrand Rheinhold, 1990.
Automatic Design Validation Framework for HDL Descriptions.. - Zhang, Hsiao, Ghosh (Correct)
No context found.
B. Beizer. Software Testing Techniques (2nd ed.). Van Nostrand Rheinold, New York, 1990.
UML-Based Integration Testing - Jean Hartmann College (2000) (5 citations) (Correct)
No context found.
Beizer, Boris, Software Testing Techniques, Second Edition. Van Nostrand Reinhold, 1990.
Function Test Framework for Testing IO-Blocks in a.. - Pitzek, Puschner (Correct)
No context found.
B. Beizer. Software Testing Techniques. Second Edition. Van Nostrand Reinhold, New York, 1990.
Fault Models and Test Generation for Hardware-Software.. - Ian Harris Department (Correct)
No context found.
B. Beizer, Software Testing Techniques, Second Edition, Van Nostrand Reinhold, 1990.
A Validation Fault Model for Timing-Induced Functional Errors - Qiushuang Zhang And (2001) (1 citation) (Correct)
No context found.
B. Beizer. Software Testing Techniques, Second Edition. Van Nostrand Reinhold, 1990.
Software Tools for Technology Transfer manuscript No. - Will Be Inserted (Correct)
No context found.
B. Beizer. Software Testing Techniques. Van Nostrand Reinhold, New York, 2nd edition, 1990.
from Closed Specifications of Classes - Wee Kheng Leow (Correct)
No context found.
B. Beizer. Software Testing Techniques. Thomson Computer Press, 2nd edition, 1990.
An Application of Causal Analysis to the Software.. - Collofello, Gosalia (1993) (Correct)
No context found.
B. Beizer, Software Testing Techniques, Van Nostrand Reinhold, 1983.
Myriad: Design and Implementation of a Federated.. - Lim, Hwang.. (1995) (5 citations) (Correct)
No context found.
B. Beizer, Software Testing Techniques, Van Nostrand Reinhold, New York, 1983.
First 50 documents Next 50
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