• 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.

• 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 KIISE:Computing Practices and Letters
• /
• v.16 no.5
• /
• pp.576-580
• /
• 2010

Generally, due to the strong coherence between embedded software and hardware or peripheral software, embedded software is tested by using black-box test based on user scenario for the whole system. This paper suggests the method to coordinate between testing and debugging under consideration for difficulties on solving out the defects detected from black-box test. First of all, from test result analysis, it builds up the debugging strategies enable to trace the locations of the defect's causes. And along with the strategies, it implements the generator of test scripts to be performed on the emulator environment. Through these steps, it can coordinate embedded software testing and debugging activities.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.39C no.9
• /
• pp.880-886
• /
• 2014

Many railway signalling functions have increasingly depended on computer software with recent development in computing technology, leading to evolution into more flexible and intelligent railway signalling system. Meanwhile, software programs are likely to have many errors and the cost incurred by such errors has increased. Especially, if fatal software error occurs during railway operation, it may result in loss of lives. So the software verification and validation have become more important. It is needed for software functional safety tool to support these, but most commercial tools depend on direct access to the system's memory, resulting in many difficulties in application. Owing to such difficulties and complexity, they are rarely used in railway signalling system software validation. In this study, a new testing tool for software functional testing through an external interface that can be easily used in functional testing of software was developed. Such testing tool allows development and analysis of test cases for black-box testing through analysis of actually used interface protocols, leading to increased user convenience.

• 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

• 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 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.

• Journal of KIISE:Software and Applications
• /
• v.29 no.10
• /
• pp.694-702
• /
• 2002

An application in Component-Based Software Development (CBSD) is built by 'composing'two kinds of components; One is a component that is made by current developer himself, and the other is a component that is from other developments. We define the former as a 'White-box component' and the latter as a 'Black-box component.' The error from the composition can be said to be caused by interactions of Black-box components and White-box components. This paper proposes a new testing technique for composition errors, and applies the technique to Enterprise Java Beans component architecture. Our technique selects test cases by injecting a fault only into the specific parts of a White-box component. This specific parts for injecting a fault are selected by analyzing composition patterns, and lead to make our test cases have a good effectiveness. We show the effectiveness of our test cases through an experiment. Moreover, we also mention an automation tool for our technique.

• Journal of Korean Society for Quality Management
• /
• v.30 no.3
• /
• pp.186-194
• /
• 2002

In this paper we introduce formulae for estimating the failure rate of a large scaled software by using the Bayesian rule when a black-box random testing which selects an element(test case) at random with equally likely probability, is performed. A program or software can be treated as a mathematical function with a well-defined (input)domain and range. For a large scaled software, their input domains can be partitioned into multiple subdomains and exhaustive testing is not generally practical. Testing is proceeding with selecting a subdomain, and then picking a test case from within the selected subdomain. Whether or not the proportion of selecting one of the subdomains is assumed probability, we developed the formulae either case by using Bayesian rule with gamma distribution as a prior distribution.