• Journal of KIISE
• /
• v.41 no.12
• /
• pp.1013-1017
• /
• 2014

A variety of applications that are accessible through app markets provide useful features and functions. However, those applications can present many GUI bugs due to the deficiency of testing processes. Even though various approaches have been developed for mobile app testing, GUI bugs in applications are still difficult to be identified due to the absence of efficiency, lack of automation, and necessity of access to the source code. In this paper, we propose an automated black-box testing method for efficient GUI bug detection. Our experimental results show that the proposed method achieves better code coverage and uncovers GUI bugs when compared with existing black-box testing called Monkey.

• Proceedings of the Korean Information Science Society Conference
• /
• 2002.04b
• /
• pp.382-384
• /
• 2002

컴포넌트 기 반 소프트웨어 개발에서 구현에 사용되는 각 컴포넌트의 성능을 이 해하는 것은 중요하다. 본 논문은 Black Box의 관점에서 EIB 컴포넌트의 성능을 측정하는 방댄 과 이 측정 방법을 지원하는 성능 측정 도구의 설계 구현에 대하여 설명한다 본 도구는 대상 컴포넌트에 대 한 영 향을 최소화하기 위하여 클라이언트 시스템에서 동작하여 성능을 측정할 수 있도록 설계되었다. 또한 사용자가 적은 노력으로 새로운 컴포넌트의 성능을 측정 할 수 있도록 테스트 프로그램을 자동으로 생성한다. 본 연구의 결과는 상용 컴포넌트의 시장에 등장하는 여러 컴포넌트의 성능을 객관적 인 방법으로 비교 측정 할 수 있는 효과적인 수단이 될 것으로 기대된다.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.1-16
• /
• 2006

As the size of software is getting huge, it has been impossible for testers to test all of source coed. Therefore, the method which uses information of requirements for testing has been researched and accepted. Although there are a lot of test methods based on requirement specification, each method has a different approach and coverage. So we should consider their various approach and coverage in the stage of test planning. This paper presents the empirical comparison and the result by applying various black-box testing methods to software system. For this experiment we studied five black-box testing methods including UML based specification technique. We applied the five testing methods to application system and evaluated the coverage of extracted test case.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2009.04a
• /
• pp.666-669
• /
• 2009

임베디드 시스템의 Black-Box 테스트 자동화를 위해 Test Script 기반으로 테스트를 진행하고 있는 툴이 많이 있다. Test Script 에 기술되어 있는 입력 값을 임베디드 시스템의 실제 신호로 생성하고 또 Test Script에 기술된 출력 예상 값을 검증하기 위해 임베디드 시스템의 출력 신호를 읽어 들이기 위해서 일반적으로 DAQ Board를 사용한다. 이 때 다양 한 DAQ Board 또는 다른 장치를 제어하기 Service 라는 레이어를 두어 다양한 장치에 상응하는 프로그램을 만들 수 있도록 하였다. 본 논문에서는 Test Script 실행에 있어 실시간 성을 최대한 보장하기 위해 각 Service 의 실행시간을 최소화 하는 방법에 대해 논하고자 한다. 논의를 하는데 있어 다양한 Service 중 NIDAQ Board를 이용하여 신호를 생성하고 읽어 들이는 Service가 모든 테스트에 있어 일반적으로 사용하게 되는 Service 이기에 이를 기준으로 Service의 실행 시간을 최소화 하는 방법을 구현 하였다.

• Journal of KIISE:Software and Applications
• /
• v.36 no.9
• /
• pp.706-717
• /
• 2009

A web application is implemented by reusing the library provided by framework and has hierarchical architecture. Also, to deal with the user request from a screen, the web application has an execution flow, called 'Business Logic', which starts with a screen, executes its composed component and comes back to the screen via database. To test web application effectively, it should reflect the characteristics of web application. In this paper we propose to test web applications via user screens with the black-box testing approach and verify its source codes with the web interface white-box test coverage that covers all the business logics of the test target and their corresponding interfaces. We analyze the proposing testing method through its tool: Testopiacov.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.2
• /
• pp.19-29
• /
• 2008

In case of unit testing, White-box test can be used to closely check source code and to analyze logic and statement errors. On the other hand, in case of function testing of system level, Black-box test can be mainly used to compare actual and expected results by inputting test data because the scale of function is large. This Black-Box test in system testing level has problem in tracing errors in source code when we find errors. Moreover applying White-box test is not easy for system testing level because the levels of test target are different. Therefore this paper suggests the vertical test method of a practical and integrated system level which can checks up to source code level using White-box test style although it aims to test the highly abstract level like a system function. In addition, the experiment explains how to apply the vertical test by displaying an example which traces from UML specification model to the source code and also shows efficiency of error trace.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.18 no.2
• /
• pp.163-168
• /
• 2018

In this paper, we propose and develop a test automation program tool that automates GUI based testing using black box testing technique in Windows environment. The main features of the proposed test automation program tool are as follows. First, an error condition is designated as an image, a screen is captured for each test step, and an error message is detected through comparison of image similarity. Second, the proposed system supports various setting options such as event waiting time during execution and coordinate increment value between each test step. Such black box test automation research was common in environments such as Android and Web, but not in Windows environment. The results of performance evaluation show that the proposed system performs GUI test automation as an image comparison module and confirms that the test is performed normally by confirming process status and error image detection.

• Journal of KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.741-749
• /
• 2004

Component users must customize components they obtain from providers, in order to fit them to their own purposes. Normally, a component consists of black-box parts and white-box parts. Component users customize a component by modifying white-box parts of a component, and the customization faults appear through the interaction between black-box parts and white-box parts. Customization testing could be an integration testing of these two parts of a component. Also, customization testing in CBSD should select effective test data to reduce the testing cost, since CBSD aims to reduce the development cost. Therefore, this paper proposes a customization testing technique based on COM architecture through analyzing many COM components, and the technique selects effective test data. This paper evaluates the effectiveness of the test data selected by the proposed technique through an empirical study. It applies the techlique to a large-scale component-based system, Chamois, and it shows that the technique enables us to test customized COM components that run in a real component-based system

• 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 military operations research society of Korea
• /
• v.24 no.2
• /
• pp.57-74
• /
• 1998

This paper is aimed to propose an testing and evaluation strategy and plan in Military Information Systems, especially focusing on development an“New-generation Wargame Model”. Through this research, we concluded that the effective and efficient testing/evaluation strategy/plan can aid the productivity, maintainability, availability, etc., of the Militray Information Systems. Highlights of the proposed testing and evaluation strategy and plan for Military Information Systems are as follows. First, in the unit and module integration testing phase, hybrid of black-box and white-box testing techniques are available for Military Information Systems and progressive approach for module integration phase should be considered because of the complexity. Second, in the system testing phase, integrated module should be tested with respect to the function and performance that should be satisfied with the user requirements, specifications, risk analysis, etc., Third, in the acceptance testing phase, reliability, interoperability, maintainability, availability, integrity, etc., must be considered in the actual or mini-operational environments for testing efficiently and effectively.