The category-partition method for specifying and generating fuctional tests

Ostrand, Thomas J.; Balcer, Marc J.

doi:10.1145/62959.62964

Cited by 624 publications

(360 citation statements)

References 5 publications

Supporting

Mentioning

352

Contrasting

Unclassified

Order By: Relevance

“…A somewhat different way to view the failure rate data is by breaking up aggregate failure rates into separate failure rates grouped by the type of call or function [29]. This gives some general insight into the portions of the implementations that tend to be robust at handling exceptions without becoming bogged down in the details of individual call/ function failure rates.…”

Section: Failure Rates By Call/function Categorymentioning

confidence: 99%

The exception handling effectiveness of POSIX operating systems

Koopman

DeVale

2000

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

AbstractÐOperating systems form a foundation for robust application software, making it important to understand how effective they are at handling exceptional conditions. The Ballista testing system was used to characterize the handling of exceptional input parameter values for up to 233 POSIX functions and system calls on each of 15 widely used operating system (OS) implementations. This identified ways to crash systems with a single call, ways to cause task hangs within OS code, ways to cause abnormal task termination within OS and library code, failures to implement defined POSIX functionality, and failures to report unsuccessful operations. Overall, only 55 percent to 76 percent of the exceptional tests performed generated error codes, depending on the operating system being tested. Approximately 6 percent to 19 percent of tests failed to generate any indication of error despite exceptional inputs. Approximately 1 percent to 3 percent of tests revealed failures to implement defined POSIX functionality for unusual, but specified, situations. Between 18 percent and 33 percent of exceptional tests caused the abnormal termination of an OS system call or library function, and five systems were completely crashed by individual system calls with exceptional parameter values. The most prevalent sources of these robustness failures were illegal pointer values, numeric overflows, and end-of-file overruns. There is significant opportunity for improving exception handling within OS calls and especially within C library functions. However, the role of signals vs. error return codes is both controversial and the source of divergent implementation philosophies, forming a potential barrier to writing portable, robust applications.

show abstract

Section: Failure Rates By Call/function Categorymentioning

confidence: 99%

The exception handling effectiveness of POSIX operating systems

Koopman

DeVale

2000

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

show abstract

“…Tests are produced based on abstract test cases from high-level system specifications written in standardized specification languages such as UML. This transformation is performed based on existing algorithms [15] combined with different test coverage strategies [16]. The results are unprecedented guarantees and automation [17].…”

Section: Figure 1 Existing Test Approachesmentioning

confidence: 99%

“…The system behavior data specifies the data set used during the tests. In particular, tedeso uses the category partition method [15], which prescribes a set of categories (data classes) and choices (data instances) of these categories. When associated with behavioral models by means of notes, categories and choices will determine the generated tests covering different sets of choices and/or paths in the models.…”

Section: B Imbt Main Elementsmentioning

confidence: 99%

An Integrated Model-Driven Approach for Mechatronic Systems Testing

Filho

Budnik

2012

2012 IEEE Fifth International Conference on Software Testing, Verification and Validation

View full text Add to dashboard Cite

Abstract-Mechatronic systems integrate mechanical, electrical and software subsystems. They are increasingly important in mission-critical infrastructures in different domains including automotive, healthcare, energy and transportation sectors. As such, the adequate testing and validation of such infrastructures are of prime importance. Mechatronic systems testing has been supported by different isolated industrial and research approaches including automated test infrastructures, model-based testing, and test execution engines. While these approaches have individual benefits, they are usually applied in isolation, suffering from different weaknesses. This paper reports on an integrated model-driven approach for mechatronic systems testing, where existing approaches are combined and enhanced. The result is unprecedented levels of automation and testability. We discuss the design and implementation of our approach, illustrating its use with a hybrid calculator example.

show abstract

“…Several sequential versions of each of these programs are available. The first three programs are provided with JUnit test suites, and the last two are provided with TSL (Test Specification Language) test suites [29]. Table I lists, for each of our objects of analysis, data on its associated "Versions" (the number of versions of the object program), "Classes" (the number of class files in the latest version of that program), "Size (KLOCs)" (the number of lines of code in the latest version of the program), and "Test Cases" (the number of test cases available for the latest version of the program).…”

Section: A Objects Of Analysismentioning

confidence: 99%

Adaptive Regression Testing Strategy: An Empirical Study

Arafeen

2011

2011 IEEE 22nd International Symposium on Software Reliability Engineering

View full text Add to dashboard Cite

Abstract-When software systems evolve, different amounts and types of code modifications can be involved in different versions. These factors can affect the costs and benefits of regression testing techniques in different ways, and thus, there may be no single regression testing technique that is the most cost-effective technique to use on every version. To date, many regression testing techniques have been proposed, but no research has been done on the problem of helping practitioners systematically choose appropriate techniques on new versions as systems evolve. To address this problem, we propose adaptive regression testing (ART) strategies that attempt to identify the regression testing techniques that will be the most cost-effective for each regression testing session considering organization's situations and testing environment. To assess our approach, we conducted an experiment focusing on test case prioritization techniques. Our results show that prioritization techniques selected by our approach can be more cost-effective than those used by the control approaches.

show abstract

The category-partition method for specifying and generating fuctional tests

Cited by 624 publications

References 5 publications

The exception handling effectiveness of POSIX operating systems

The exception handling effectiveness of POSIX operating systems

An Integrated Model-Driven Approach for Mechatronic Systems Testing

Adaptive Regression Testing Strategy: An Empirical Study

Contact Info

Product

Resources

About