On the relationship between two control-flow coverage criteria: all JJ-paths and MCDC

Woodward, Martin R.; Hennell, M.A.

doi:10.1016/j.infsof.2005.05.003

Cited by 32 publications

(16 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Modified Condition Decision Coverage (MCDC), defined in the RTCA/DO-178B standard [8], is a broadly studied structural coverage criterion [31], [32]. It has also Name = "GT_Device1" Obligated = "ServiceProvider" <Scope serviceName = "WSMedicalDevice" method = "getMeasure" </Scope> <QualifyingCondition> idDevice = device_1 </QualifyingCondition> <ServiceLevelObjective> responseTime <= 3 seconds </ServiceLevelObjective> </GuaranteeTerm> <GuaranteeTerm Name = "GT_Device2" Obligated = "ServiceProvider" <Scope serviceName = "WSMedicalDevice" method = "getMeasure" </Scope> <QualifyingCondition> idDevice = device_2 </QualifyingCondition> <ServiceLevelObjective> responseTime <= 10 seconds </ServiceLevelObjective> </GuaranteeTerm>…”

Section: Four-valued Mcdc Test Criterionmentioning

confidence: 99%

Coverage-Based Testing for Service Level Agreements

Palacios

García-Fanjul

Tuya

et al. 2015

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

This is the accepted version of the paper.This version of the publication may differ from the final published version. Abstract-Service Level Agreements (SLAs) are typically used to specify rules regarding the consumption of services that are agreed between the providers of the Service-Based Applications (SBAs) and their consumers. An SLA includes a list of terms that contain the guarantees that must be fulfilled during the provisioning and consumption of the services. Since the violation of such guarantees may lead to the application of potential penalties, it is important to assure that the SBA behaves as expected. Permanent repository linkIn this article, we propose a proactive approach to test SLA-aware SBAs by means of identifying test requirements, which represent situations that are relevant to be tested. To address this issue, we define a four-valued logic that allows evaluating both the individual guarantee terms and their logical relationships. Grounded in this logic, we devise a test criterion based on the Modified Condition Decision Coverage (MCDC) in order to obtain a cost-effective set of test requirements from the structure of the SLA. Furthermore by analyzing the syntax and semantics of the agreement, we define specific rules to avoid non-feasible test requirements. The whole approach has been automated and applied over an eHealth case study.

show abstract

Section: Four-valued Mcdc Test Criterionmentioning

confidence: 99%

Coverage-Based Testing for Service Level Agreements

Palacios

García-Fanjul

Tuya

et al. 2015

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

show abstract

“…In modern programming languages compound decisions must be converted to a series of simple ones, thus enforcing the introduction of additional nodes and edges for their representation. Details of the effects of such incidents can be found in [9].…”

Section: Notation and Terminologymentioning

confidence: 99%

Mutation based test case generation via a path selection strategy

Papadakis

Malevris

2012

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Generally, mutation analysis has been identified as a powerful testing method. Researchers have shown that its use as a testing criterion exercises quite thoroughly the system under test while it achieves to reveal more faults than standard structural testing criteria. Despite its potential, mutation fails to be adopted in a widespread practical use and its popularity falls significantly short when compared with other structural methods. This can be attributed to the lack of thorough studies dealing with the practical problems introduced by mutation and the assessment of the effort needed when applying it. Such an incident, masks the real cost involved preventing the development of easy and effective to use strategies to circumvent this problem. Objective: In this paper, a path selection strategy for selecting test cases able to effectively kill mutants when performing weak mutation testing is presented and analysed. Method: The testing effort is highly correlated with the number of attempts the tester makes in order to generate adequate test cases. Therefore, a significant influence on the efficiency associated with a test case generation strategy greatly depends on the number of candidate paths selected in order to achieve a predefined coverage goal. The effort can thus be related to the number of infeasible paths encountered during the test case generation process. Results: An experiment, investigating well over 55 million of program paths is conducted based on a strategy that alleviates the effects of infeasible paths. Strategy details, along with a prototype implementation are reported and analysed through the experimental results obtained by its employment to a set of program units. Conclusion:The results obtained suggest that the strategy used can play an important role in making the mutation testing method more appealing and practical.

show abstract

“…Genetic Algorithms (GA) were employed to provide oracles for condition coverage testing, which concerns conditional statements (Woodward and Hennell 2006). Manual searching to find test cases that increase condition coverage is difficult when the SUT has many nested decision making structures.…”

Section: Prominent Test Oraclesmentioning

confidence: 99%

Artificial neural networks as multi-networks automated test oracle

et al. 2011

View full text Add to dashboard Cite

One of the important issues in software testing is to provide an automated test oracle. Test oracles are reliable sources of how the software under test must operate. In particular, they are used to evaluate the actual results produced by the software. However, in order to generate an automated test oracle, it is necessary to map the input domain to the output domain automatically. In this paper, Multi-Networks Oracles based on Artificial Neural Networks are introduced to handle the mapping automatically. They are an enhanced version of previous ANN-Based Oracles. The proposed model was evaluated by a framework provided by mutation testing and applied to test two industry-sized case studies. In particular, a mutated version of each case study was provided and injected with some faults. Then, a fault-free version of it was developed as a Golden Version to evaluate the capability of the proposed oracle finding the injected faults. Meanwhile, the quality of the proposed oracle is measured by assessing its accuracy, precision, misclassification error and recall. Furthermore, the results of the proposed oracle are compared with former ANN-based Oracles. Accuracy of the proposed oracle was up to 98.93%, and the oracle detected up to 98% of the injected faults. The results of the study show the proposed oracle has better quality and applicability than the previous model.

show abstract

On the relationship between two control-flow coverage criteria: all JJ-paths and MCDC

Cited by 32 publications

References 13 publications

Coverage-Based Testing for Service Level Agreements

Coverage-Based Testing for Service Level Agreements

Mutation based test case generation via a path selection strategy

Artificial neural networks as multi-networks automated test oracle

Contact Info

Product

Resources

About