Reduce Testing Effort Research Articles

Improving Test Efficiency through Prioritization Based On Testing Dependency

During the various iterations of software development, test case prioritization generally schedules test cases in order to increase test efficiency as soon as possible without reducing the scale of the test. It is noted that currently, many prioritization techniques are usually based on the assumption that the test cases are independent so as to reduce testing effort. However in the actual test, the dependencies and relations exist between the test cases. In this paper, we propose a new type of prioritization technique based on the relationship of dependencies between test cases. We gather the dependency information of a test suite and then put forward a weighted depth-first search algorithm to determine the most effective order. To assess our approach, an academic feasibility study and three industrial experiments are conducted. Evaluation results indicate that our proposed method can be used to improve the fault detection effectiveness when compared with random ordering and some existed prioritization techniques which are based on function coverage.

Early software reliability analysis using reliability relevant software metrics

The early software reliability analysis is very useful for improving the quality of software at reduced testing effort. Software defect density indicator predicted in the early phases (requirement analysis, design and coding phases) provides an opportunity for the early identification of cost overrun, software development process issues and optimal development strategies. Failure data is not available in the early phases of the software development life cycle (SDLC). However, qualitative values of software metrics are available in the early phases of SDLC. Therefore, in this paper, a model is proposed to predict the software defect density indicator of early phases of SDLC using fuzzy logic and the reliability relevant software metrics of early artifacts. The proposed model is applied on twenty real software projects. It is observed that the requirement analysis phase defect density indicator value is relatively greater than that of the design and coding artifacts. The model is validated with the existing literature. Validation result is satisfactory.

분산 시스템의 기능 및 비기능 검증을 위한 테스트 프레임워크 개발

Distributed systems are collection of physically distributed computers linked by a network. General use of wired/wireless Internet enables users to make use of distributed service anytime and anywhere. The explosive growth of distributed services strongly requires functional verification of services as well as verification of non-functional elements such as service quality. In order to verify distributed services it is necessary to build a test environment for distributed systems. Because, however, distributed systems are composed of physically distributed nodes, efforts to construct a test environment are required more than those in a test environment for a monolithic system. In this paper we propose a test framework to verify functional and non-functional features of distributed systems. The suggested framework automatically generates test cases through the message sequence charts, and includes a test driver composed of the virtual nodes which can simulate the physically distributed nodes. The test result can be checked easily through the various graphs and the graphical user interface (GUI). The test framework can reduce testing efforts for a distributed system and can enhance the reliability of the system. ☞ keyword : Distributed systems, Test Framework, Functional Testing, Non-functional Testing, Quality of Service

Analyzing the relationships between inspections and testing to provide a software testing focus

ContextQuality assurance effort, especially testing effort, is frequently a major cost factor during software development. Consequently, one major goal is often to reduce testing effort. One promising way to improve the effectiveness and efficiency of software quality assurance is the use of data from early defect detection activities to provide a software testing focus. Studies indicate that using a combination of early defect data and other product data to focus testing activities outperforms the use of other product data only. One of the key challenges is that the use of data from early defect detection activities (such as inspections) to focus testing requires a thorough understanding of the relationships between these early defect detection activities and testing. An aggravating factor is that these relationships are highly context-specific and need to be evaluated for concrete environments. ObjectiveThe underlying goal of this paper is to help companies get a better understanding of these relationships for their own environment, and to provide them with a methodology for finding relationships in their own environments. MethodThis article compares three different strategies for evaluating assumed relationships between inspections and testing. We compare a confidence counter, different quality classes, and the F-measure including precision and recall. ResultsOne result of this case-study-based comparison is that evaluations based on the aggregated F-measures are more suitable for industry environments than evaluations based on a confidence counter. Moreover, they provide more detailed insights about the validity of the relationships. ConclusionWe have confirmed that inspection results are suitable data for controlling testing activities. Evaluated knowledge about relationships between inspections and testing can be used in the integrated inspection and testing approach In2Test to focus testing activities. Product data can be used in addition. However, the assumptions have to be evaluated in each new context.

Web Service Test Data Generation Using Interface Semantic Contract

PDF HTML阅读 XML下载 导出引用 引用提醒 基于接口语义契约的Web服务测试数据生成 DOI: 10.3724/SP.J.1001.2013.04366 作者: 作者单位: 作者简介: 通讯作者: 中图分类号: 基金项目: 国家自然科学基金(61073003);国家重点基础研究发展计划(973)(2001CB302505);北京市自然科学基金(4132062);清华大学自主科研计划 Web Service Test Data Generation Using Interface Semantic Contract Author: Affiliation: Fund Project: 摘要 | 图/表 | 访问统计 | 参考文献 | 相似文献 | 引证文献 | 资源附件 | 文章评论 摘要:测试是Web 服务质量保证的主要手段之一,测试自动化是降低测试代价的有效途径,测试数据生成是测试自动化研究的一个重要内容.提出采用本体及规则的知识描述语言,建立服务接口的语义契约模型(interface semantic contract,简称ISC),并探讨了基于ISC 的测试数据生成技术,给出了分区生成算法以及测试数据生成的模拟退火算法.实验结果表明,与随机测试相比,该方法能够采用10%的测试用例数量达到同样的测试覆盖率;在同样的测试用例数量上,最高可提高50%的测试覆盖率. Abstract:Testing is one of the primary methods for Web service quality control. Test automation is necessary to enhance test productivity and quality while reducing test effort. Test data generation is a critical issue of automated testing. The paper proposes a method called interface semantic contract (ISC) for modeling services' exposed functionalities using ontology and rule language. Algorithms are developed to generate input partitions and test data based on ISC. Case studies are exercised to illustrate the proposed approach. The results show that compared with conventional random testing, the proposed approach can enhance test coverage by 50% with the same number of test cases, and reduce test effort by 90% to reach the same test coverage. 参考文献 相似文献 引证文献

Reducing test effort: A systematic mapping study on existing approaches

ContextQuality assurance effort, especially testing effort, is often a major cost factor during software development, which sometimes consumes more than 50% of the overall development effort. Consequently, one major goal is often to reduce testing effort. ObjectiveThe main goal of the systematic mapping study is the identification of existing approaches that are able to reduce testing effort. Therefore, an overview should be presented both for researchers and practitioners in order to identify, on the one hand, future research directions and, on the other hand, potential for improvements in practical environments. MethodTwo researchers performed a systematic mapping study, focusing on four databases with an initial result set of 4020 articles. ResultsIn total, we selected and categorized 144 articles. Five different areas were identified that exploit different ways to reduce testing effort: approaches that predict defect-prone parts or defect content, automation, test input reduction approaches, quality assurance techniques applied before testing, and test strategy approaches. ConclusionThe results reflect an increased interest in this topic in recent years. A lot of different approaches have been developed, refined, and evaluated in different environments. The highest attention was found with respect to automation and prediction approaches. In addition, some input reduction approaches were found. However, in terms of combining early quality assurance activities with testing to reduce test effort, only a small number of approaches were found. Due to the continuous challenge of reducing test effort, future research in this area is expected.

On Testing and Evaluating Service-Oriented Software

As service-oriented architecture matures and more Web services become available, developers must test an ever-increasing volume of services. A framework that defines and evaluates test-case potency based on coverage relationships can reduce testing effort while maintaining testing's effectiveness.

Bayesian reliability demonstration for systems with redundancy

Zero-failure testing for Bayesian reliability demonstration (BRD) is studied, aiming at minimal expected costs of testing and process failure. For the process after testing, reliability is formulated in terms of failure-free periods, based on the assumption that failure in the process would be catastrophic, causing the process to be discontinued and incurring high costs. BRD is considered for systems with redundancy, which are required to perform multiple independent types of task. Optimal BRD testing is also considered in combination with flexibility in the system redundancy, where more components can be installed to reduce test effort. Attention is restricted to systems with exchangeable components, with testing only at the component level. Generalizations are briefly discussed at the end of this paper.

A promising approach to two-person software review in educational environment

Technical review is a type of software review which effectively reduces testing effort and detects faults more effectively than testing. Thus, it should be learned by all persons that are engaged in software development in educational environments. In this paper, we propose a new approach which allows every person to effectively learn the review methods in educational environments. In the proposed approach, the review is done by a pair of persons: producer and reviewer. For each product, first, the producer explains the product to the reviewer and receives questions about it from the reviewer; then, both the producer and the reviewer jointly check the product to detect faults by using a checklist. Then, we have applied the proposed method to an experimental project in 1994. Comparing the result of the experiment to results of an experimental project in 1993 in which the conventional review method was applied, the following advantages were found: (1) Contributions from each individual increased, (2) Every person learned the review methods easily, (3) Percentage of unreviewed product decreased, (4) Review effort decreased by 30%, and (5) Completion rate increased by 10%. Thus, the proposed approach is useful for not only the educational environment but also for actual software development.

The assessment of explosion hazards from electrical equipment on aircraft in the light of elementary probability theory

The paper discusses the influence of statistical considerations on the design of tests intended to lead to an assessment of the explosion risks arising from the normal operation of electrical equipment on aircraft The statistical approach implies that a finite amount of testing cannot establish a nil risk, the amount of testing depends upon the degree of assurance required. It is shown that an apparently ‘reasonable’ degree of assurance leads to an unmanageable amount of test effort if the tests are made under fully simulated service conditions.Test effort can be reduced by orders of magnitude if it is possible to assess separately each of several factors that are simultaneously necessary for an explosion Testing can be further reduced when it is possible to speed up the operation of the unit for test purposes. The proposition that test effort may be reduced by using ‘enhanced’ test conditions is considered. In this Connection, dependence on extrapolation procedures is particularly criticized.It is noted that standardization of enclosures for equipment would much reduce test effort. The advantage in relieving the test situation, of dependence on sealed enclosures that need only mechanical testing is emphasized.