• Journal of Computing Science and Engineering
• /
• 제9권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.

• 정보처리학회논문지D
• /
• 제13D권4호
• /
• pp.573-582
• /
• 2006

소프트웨어를 블랙박스 테스트 하려면 대상 소프트웨어에 적절한 데이터를 주어 실행해 보아야 한다. 효과적인 테스트가 되기 위해서 테스트 케이스의 선택뿐만 아니라 테스트 케이스가 어떻게 표현되었는가가 중요하다. 또한 정적인 테스트 작업에도 테스트를 위한 체크리스트가 어떻게 작성되었는지에 따라 테스트 작업의 효율성이 좌우된다. 이 논문에서는 비효율적이며 문제가 있는 테스트 케이스와 체크 리스트들을 리엔지니어링 하는 방법을 제시하고 이를 실험 하였다. 임베디드 시스템의 일종인 디지털 방송수신 장치에 탑재된 소프트웨어를 대상으로 하여 이미 사용 중인 테스트 케이스의 효율성과 적합성을 따져보고 이를 리엔지니어링 하였다. 리엔지니어링 한 후의 테스트 케이스의 산출물이 테스트 시간과 커버리지 측면에서 얼마나 효과적인지를 살펴보았다. 또한 제품 계열 개념의 소프트웨어를 테스트하기에 적합하도록 테스트 케이스를 재사용 또는 재구조화 하는 방법도 연구하였다.

• 한국군사과학기술학회지
• /
• 제23권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.

• 한국IT서비스학회지
• /
• 제10권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
• /
• 제8권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.

• 대한족부족관절학회지
• /
• 제15권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.

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제8권6호
• /
• pp.235-242
• /
• 2019

본 논문에서는 제어기 기능이 표현 된 변경된 MATLAB Simulink/Stateflow(SL/SF) 모델의 재사용 가능한 테스트 케이스 도출 기법을 제안한다. 자동차의 ECU(Electrical Control Unit)와 같이 복잡한 SL/SF 모델의 테스트 케이스를 작성하는데 많은 시간과 노력이 필요하다. 모델이 수정 될 때마다 새로 만들어낼 테스트 케이스를 줄이기 위한 직관적인 방법은 수정 전 모델에서 생성한 테스트 케이스 중 일부를 재사용하는 것이다. 본 논문에서는 모델 행동을 정의하고 테스트 케이스 별 모델 동등성을 판단하여 수정 후 SL/SF에 재사용 가능한 테스트 케이스를 도출하는 방법을 제안한다. 제안된 테스트 케이스 재사용 기법은 상용 자동차 제어기 모델을 이용하여 성능을 평가한다.

• 정보처리학회논문지D
• /
• 제17D권1호
• /
• pp.41-52
• /
• 2010

생성된 테스트 케이스와 요구사항과의 연관관계가 중요하지만, 모델을 이용한 테스트 케이스 자동생성에서는 모델이 요구사항과 m:n의 관계를 맺기 때문에 테스트 케이스와 요구사항과의 관계도 매우 복잡해진다. 본 논문에서는 1:1 모델링 도구인 REED(REquirement EDitor)를 이용하여 테스트 케이스를 생성하는 방법에 대하여 기술한다. 테스트 케이스는 커버리지 타겟 생성, IORT(Input Output Relation Tree) 생성, 테스트 케이스 생성의 3단계를 거치며, 모든 단계는 자동으로 진행된다. 생성된 테스트 케이스는 하나의 요구사항에서 생성될 수 있으며 실제 시스템에 적용한 결과, 온도조절장치 경우는 5,566개, 버스카드 단말기의 경우는 3,757개, 굴착기 제어기는 4,611개의 테스트 케이스가 생성되었다.

• 대한수의학회지
• /
• 제32권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.

• 스마트미디어저널
• /
• 제13권8호
• /
• pp.9-15
• /
• 2024

소프트웨어 테스트는 소프트웨어 개발 프로세스의 필수적인 부분이다. 특히 MC/DC(Modified Condition / Decision Coverage)는 복잡한 조건과 결정 구조를 효과적으로 검증하여 소프트웨어의 안정성과 신뢰성을 높이는 데 사용된다. 본 연구에서는 MC/DC 수행의 최대 커버리지 값 확인을 위해 2진수를 활용한 MCC(Multiple Condition Coverage) 테스트 케이스 생성하는 MTC(MCC Test Cases) 생성기를 제안한다. 제안한 MTC 생성기는 TCAS(Traffic alert and Collision Avoidance System)-II 명세서 조건의 일부를 사용하여 CSV(Comma-Separated Values) 파일로 변환 후, VectorCAST 프로그램을 통해 커버리지 결과를 확인하였다. 그 결과 MCC 테스트 케이스로 MC/DC를 수행하여 TCAS-II 명세서의 각 조건들의 MC/DC 수행 시 최대 커버리지 값을 확인하였다. 이는 MC/DC 수행 시 커버리지 최댓값을 확인 함으로써 MC/DC 테스트 케이스 검증 연구에 도움이 된다. 또한 더 많은 테스트 케이스를 통해 결함발견 가능성도 증가시킨다. 이를 통해 소프트웨어 테스트의 커버리지 검증의 효율성과 소프트웨어의 품질 및 안정성을 향상하는 데 기여할 수 있다.