• Journal of Computing Science and Engineering
• /
• v.9 no.3
• /
• pp.142-154
• /
• 2015

Fault localization techniques help locate faults in source codes by exploiting collected test information and have shown promising results. To precisely locate faults, the techniques require a large number of test cases that sufficiently exercise the executable statements together with the label information of each test case as a failure or a success. However, during the process of software development, developers may not have high-coverage test cases to effectively locate faults. With the test case generation techniques, a large number of test cases without expected outputs can be automatically generated. Whereas the execution results for generated test cases need to be inspected by developers, which brings much manual effort and potentially hampers fault-localization effectiveness. To address this problem, this paper presents a method to select a few test cases from a number of test cases without expected outputs for result inspection, and in the meantime selected test cases can still support effective fault localization. The experimental results show that our approach can significantly reduce the number of test cases that need to be inspected by developers and the effectiveness of fault localization techniques is close to that of whole test cases.

• The KIPS Transactions:PartD
• /
• v.13D no.4 s.107
• /
• pp.573-582
• /
• 2006

Black-box testing needs to prepare fitting test data, execute software, and examine the result. If we test software effectively, not only selecting test cases but also representing test cases are important. In static testing effectiveness of testing activities also depends on how to represent test cases and checklist to validate. This paper suggests a method for finding ineffective critical test cases and reengineering them. An experiment of reengineering digital set-top box software shows the process and results of checking effectiveness and conformance of current test cases and patching test cases. The result shows how much save the test time and improve test coverage by reengineering test cases. Methods of reuse and restructuring test cases are also studied to fit into embedded product-line software.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.23 no.4
• /
• pp.389-398
• /
• 2020

Test cases in the existing weapon system software were created manually by the tester analyzing the test items defined in the software integration test procedure. However, existing test case generation method has two limitations. First, the quality of test cases can vary depending on the tester's ability to analyze the test items. Second, excessive time and cost may be incurred in writing test cases. This paper proposes a method to automatically generate test cases based on the requirements model and specifications to overcome the limitations of the existing weapon system software test case generation. Generate test sequences and test data based on the use case event model, a model representing the requirements of the weapon system software, and the use case specification specifying the requirements. The proposed method was applied to 8 target models constituting the avionics control system, producing 30 test sequences and 8 test data.

• Journal of Information Technology Services
• /
• v.10 no.4
• /
• pp.205-218
• /
• 2011

Unit testing which is the first task to perform software testing has a major impact on reducing s/w development cost and improving s/w quality. In order to make unit testing become the formal procedure rather than ad-hoc tasks performed by developer, the language-neutral measures are necessary in the programming which is able to specify the test cases. This paper presents a test assertion language for the language-neutral specification of the test cases. The suggested language is based on the ISO/IEC 24709-1, but it supports object oriented features and can describe test cases for unit testing. The test cases that are specified by the language can be used for generating test oracle source codes by test oracle generation tools.

• Journal of Information Processing Systems
• /
• v.8 no.2
• /
• pp.213-240
• /
• 2012

Safety critical systems, real time systems, and event-based systems have a complex set of events and their own interdependency, which makes them difficult to test ma Safety critic Safety critical systems, real time systems, and event-based systems have a complex set of events and their own interdependency, which makes them difficult to test manually. In order to cut down on costs, save time, and increase reliability, the model based testing approach is the best solution. Such an approach does not require applications or codes prior to generating test cases, so it leads to the early detection of faults, which helps in reducing the development time. Several model-based testing approaches have used different UML models but very few works have been reported to show the generation of test cases that use events. Test cases that use events are an apt choice for these types of systems. However, these works have considered events that happen at a user interface level in a system while other events that happen in a system are not considered. Such works have limited applications in testing the GUI of a system. In this paper, a novel model-based testing approach is presented using business events, state events, and control events that have been captured directly from requirement specifications. The proposed approach documents events in event templates and then builds an event-flow model and a fault model for a system. Test coverage criterion and an algorithm are designed using these models to generate event sequence based test scenarios and test cases. Unlike other event based approaches, our approach is able to detect the proposed faults in a system. A prototype tool is developed to automate and evaluate the applicability of the entire process. Results have shown that the proposed approach and supportive tool is able to successfully derive test scenarios and test cases from the requirement specifications of safety critical systems, real time systems, and event based systems.

• Journal of Korean Foot and Ankle Society
• /
• v.15 no.1
• /
• pp.22-26
• /
• 2011

Purpose: To report the effectiveness of adding distal fibular external rotation stress test on the traditional lateral stress Cotton test in evaluating distal tibiofibular syndesmotic injuries. Materials and Methods: We evaluated syndesmotic injuries with intraoperative stress test during treating ankle fractures from March 2009 to September 2010. External rotation of distal fibula using small elevator was added on traditional stress test in case of suspicious syndesmotic injury. We retrospectively reviewed and compared the results of each test in 44 cases for which we tried both tests. Results: In 9 cases of positive traditional lateral stress tests, positive results were obtained in all cases by additional external rotation tests. In 21 cases of negative traditional stress tests, additional stress tests results were also negative. But there were 10 cases of positive additional tests and 4 of negative additional tests in equivocal results cases by the traditional stress tests. Conclusion: Using additional external rotation stress test in case of equivocal test result by the traditional lateral stress Cotton test for evaluation of syndesmotic injury during operation for ankle fracture can be a supplemental method to clarify syndesmotic injury needs fixation.

• KIPS Transactions on Software and Data Engineering
• /
• v.8 no.6
• /
• pp.235-242
• /
• 2019

This paper proposes a reusable test case extraction technique for modified MATLAB Simulink/Stateflow (SL/SF) model. Creating test cases for complicated SL/SF model like ECU(Electrical Control Unit) of automotive, requires a lot of time and effort. An intuitive way to reduce to create new test cases whenever the model changes, is to reuse some test cases which have been generated for the original model. In this paper, we propose a method to define reusable test cases in SL/SF after defining model behavior and judging model equality by test cases. The proposed technique is evaluated using a commercial automotive controller model.

• The KIPS Transactions:PartD
• /
• v.17D no.1
• /
• pp.41-52
• /
• 2010

A relation between generated test cases and an original requirement is important, but it becomes very complex because a relation between requirement models and requirements are m-to-n in automatic test case generation based on models. In this paper, I suggest automatic generation technique for REED (REquirement EDitor), 1-to-1 requirement modeling tool. Test cases are generated though 3 steps, Coverage Target Generation, IORT (Input Output Relation Tree)Generation, and Test Cases Generation. All these steps are running automatically. The generated test cases can be generated from a single requirement. As a result of applying to three real commercial systems, there are 5566 test cases for the Temperature Controller, 3757 test cases for Bus Card Terminal, and 4611 test cases for Excavator Controller.

• Korean Journal of Veterinary Research
• /
• v.32 no.4
• /
• pp.641-647
• /
• 1992

This study was conducted to determine the serum antibodies against toxoplasma in the artificially infected dogs, pet and street dogs by latex agglutination (LA) and indirect fluorescent antibody (IFA) test. LA test was carried out with commercial Toxo-MT kit (Eiken chemical Co.) and IFA test was carried out with rabbit-anti-dog IgG labelled with FITC (Cappel Co.) and toxo-antigen slides prepared in laboratory. The results obtained were as follows ; 1. Antibodies to Toxoplasma gondii in the artificially infected dogs were detected firstly at the Day 8 in IFA and Day 9 in LA test after inoculation. Positive antibody reactions by these tests were declined gradually afterward but maintained up to 12 weeks. 2. In LA test serum antibody titers in 310 test sera were shown as 10 cases(32%) in 1 : 32.5(1.0%) in 1 : 64, 4(1.3%) in 1 : 128 and 2(0.7%) in 1 : 256. In IFA test serum antibody titers 310 test sera were shown as 17 cases(5.5%) in 1 : 64, 8(2.6%) in 1 : 128 and 5(1.6%) in 1 : 256. 3. In the total of 310 sera from pet and street dogs toxoplasma antibody positive rates were 21 cases (6.8%) by LA and 30 cases (9.7%) by IFA test and the positive detection rates between these two groups by LA and IFA test were not significant(p<0.05). 4. In the total of 115 sera from pet dogs toxoplasma antibody positive rates were 12 cases(10.4%) by LA and 15(13.0%) by IFA test. And in the 195 street dogs the positive rates were 9 cases(4.6%) by LA and 15(7.7%) by IFA test. Also, the positive detection rates between these two groups by LA and IFA test were not significant(p<0.05). 5. Agreement of reactivity between LA and IFA test for 310 sera was 91.3% in total of 283 cases consisting of 12 cases(3.9%) of both LA and IFA positive and 271 cases(87.4%) of LA and IFA negative. 6. LA test was almostly equivalent to the IFA test in producibility and proved to be a simple tool for the screening of toxoplasma antibody in laboratory.

• KIPS Transactions on Software and Data Engineering
• /
• v.6 no.8
• /
• pp.401-410
• /
• 2017

This paper proposes a method to generate test cases in an automatic manner, based on checklist containing test cases used for testing embedded systems. In general, the items to be tested are defined in a checklist. However, most test case generation strategies recommend to test a system with not only the defined test items but also various mutated test conditions. The proposed method parses checklist in Korean file and figures out the system inputs and outputs, and operation information. With the found information and the user defined test case generation strategy, the test cases are automatically generated. With the proposed method, the errors introduced during manual test case generation may be reduced and various test cases not defined in checklist can be generated. The proposed method is implemented and the experiment is performed with the checklist for an medical embedded system. The feasibility of the proposed method is shown through the test cases generated from the checklist. The test cases are adequate to the coverages and their statistics are correct.