Identifying Test Requirements by Analyzing SLA Guarantee Terms

Palacios, Marcos; García-Fanjul, José; Tuya, Javier; Spanoudakis, George

doi:10.1109/icws.2012.78

Cited by 8 publications

(8 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In a previous work we dealt with the identification of test requirements by means of analyzing the information contained in the individual guarantee terms [7]. In this article, we are providing a further step in the sense that we tackle the testing of the logical combinations of the terms represented through the compositors.…”

Section: Definition 1 An Evaluation Value Is the Output Provided By mentioning

confidence: 99%

See 1 more Smart Citation

Coverage-Based Testing for Service Level Agreements

Palacios

García-Fanjul

Tuya

et al. 2015

IEEE Trans. Serv. Comput.

Self Cite

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: Definition 1 An Evaluation Value Is the Output Provided By mentioning

confidence: 99%

“…In a previous work we addressed the identification of test requirements by analyzing the individual guarantee terms of the SLA [7]. These test requirements represent error-prone situations that are interesting to be tested.…”

Section: Introductionmentioning

confidence: 99%

Coverage-Based Testing for Service Level Agreements

Palacios

García-Fanjul

Tuya

et al. 2015

IEEE Trans. Serv. Comput.

Self Cite

View full text Add to dashboard Cite

show abstract

“…In previous research [27], we have developed a four-valued logic and defined a method to identify a set of test values from the information contained in the SLA Guarantee Terms.…”

Section: Evaluation Of Sla Guarantee Termsmentioning

confidence: 99%

“…In that work, our aim was to combine the advantages of both proactive and reactive approaches [26]. Later, we addressed the identification of situations to be tested from the information contained in the individual SLA terms [27]. These situations may be used to guide the design of an appropriate test suite that exercises such situations and also to derive a monitoring plan allowing checking the compliance of the SLA at runtime.…”

Section: Introductionmentioning

confidence: 99%

“…Section 3 provides a background about the two cornerstones of this research: Software Testing standards and WS-Agreement. It also summarizes the four-valued logic used to evaluate SLA Guarantee Terms, which was previously developed by the authors [27] and is again used in this article. Section 4 discusses the generation of test cases and the level of automation provided by SLACT.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Automatic test case generation for WS-Agreements using combinatorial testing

Palacios

García-Fanjul

Tuya

et al. 2015

Computer Standards & Interfaces

Self Cite

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. Permanent repository link AbstractIn the scope of the applications developed under the service-based paradigm, Service Level Agreements (SLAs) are a standard mechanism used to flexibly specify the Quality of Service (QoS) that must be delivered. These agreements contain the conditions negotiated between the service provider and consumers as well as the potential penalties derived from the violation of such conditions. In this context, it is important to assure that the service based application (SBA) behaves as expected in order to avoid potential consequences like penalties or dissatisfaction between the stakeholders that have negotiated and signed the SLA. In this article we address the testing of SLAs specified using the WS-Agreement standard by means of applying testing techniques such as the Classification Tree Method and Combinatorial Testing to generate test cases. From the content of the individual terms of the SLA, we identify situations that need to be tested. We also obtain a set of constraints based on the SLA specification and the behaviour of the SBA in order to guarantee the testability of the test cases. Furthermore, we define three different coverage strategies with the aim at grading the intensity of the tests. Finally, we have developed a tool named SLACT (SLA Combinatorial Testing) in order to automate the process and we have applied the whole approach to an eHealth case study.

show abstract