Automatic generation of functional vectors using the extended finite state machine model
ACM Transactions on Design Automation of Electronic Systems (TODAES)
Foundations of algorithms using C++ pseudocode (2nd ed.)
Foundations of algorithms using C++ pseudocode (2nd ed.)
Reduced Length Checking Sequences
IEEE Transactions on Computers
A survey of communication protocol testing
Journal of Systems and Software
An Empirical Analysis of Equivalence Partitioning, Boundary Value Analysis and Random Testing
METRICS '97 Proceedings of the 4th International Symposium on Software Metrics
Confirming Configurations in EFSM Testing
IEEE Transactions on Software Engineering
A Method Enabling Feasible Conformance Test Sequence Generation for EFSM Models
IEEE Transactions on Computers
On the testability of SDL specifications
Computer Networks: The International Journal of Computer and Telecommunications Networking
Software Fault Interactions and Implications for Software Testing
IEEE Transactions on Software Engineering
Assessing and Improving State-Based Class Testing: A Series of Experiments
IEEE Transactions on Software Engineering
Robustness Testing of Java Server Applications
IEEE Transactions on Software Engineering
An extended fault class hierarchy for specification-based testing
ACM Transactions on Software Engineering and Methodology (TOSEM)
Proposal of a Method to Support Testing for Java Programs with UML
APSEC '05 Proceedings of the 12th Asia-Pacific Software Engineering Conference
Optimizing the Length of Checking Sequences
IEEE Transactions on Computers
On the Learnability of Two Representations of Equivalence Partitioning and Boundary Value Analysis
ASWEC '07 Proceedings of the 2007 Australian Software Engineering Conference
A state-based approach to integration testing based on UML models
Information and Software Technology
HCMDSS-MDPNP '07 Proceedings of the 2007 Joint Workshop on High Confidence Medical Devices, Software, and Systems and Medical Device Plug-and-Play Interoperability
Extending EFSMs to Specify and Test Timed Systems with Action Durations and Time-Outs
IEEE Transactions on Computers
A Comparative Evaluation of Tests Generated from Different UML Diagrams
SNPD '08 Proceedings of the 2008 Ninth ACIS International Conference on Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing
An Approach to Transforming UML Model to FSM Model for Automatic Testing
CSSE '08 Proceedings of the 2008 International Conference on Computer Science and Software Engineering - Volume 02
Generating Feasible Transition Paths for Testing from an Extended Finite State Machine (EFSM)
ICST '09 Proceedings of the 2009 International Conference on Software Testing Verification and Validation
Conformance Testing of Temporal Role-Based Access Control Systems
IEEE Transactions on Dependable and Secure Computing
IEEE Transactions on Software Engineering
Software Testing: A Craftsman's Approach
Software Testing: A Craftsman's Approach
Experience with teaching black-box testing in a computer science/software engineering curriculum
IEEE Transactions on Education
Hi-index | 0.00 |
As medical software is getting larger-sized, complex, and connected with other devices, finding faults in integrated software modules gets more difficult and time consuming. Existing integration testing typically takes a black-box approach, which treats the target software as a black box and selects test cases without considering internal behavior of each software module. Though it could be cost-effective, this black-box approach cannot thoroughly test interaction behavior among integrated modules and might leave critical faults undetected, which should not happen in safety-critical systems such as medical software. This work anticipates that information on internal behavior is necessary even for integration testing to define thorough test cases for critical software and proposes a new integration testing method by reusing test cases used for unit testing. The goal is to provide a cost-effective method to detect subtle interaction faults at the integration testing phase by reusing the knowledge obtained from unit testing phase. The suggested approach notes that the test cases for the unit testing include knowledge on internal behavior of each unit and extracts test cases for the integration testing from the test cases for the unit testing for a given test criteria. The extracted representative test cases are connected with functions under test using the state domain and a single test sequence to cover the test cases is produced. By means of reusing unit test cases, the tester has effective test cases to examine diverse execution paths and find interaction faults without analyzing complex modules. The produced test sequence can have test coverage as high as the unit testing coverage and its length is close to the length of optimal test sequences.