Fault-based test suite prioritization for specification-based testing

ReuseThis article is distributed under the terms of the Creative Commons Attribution-NonCommercial-NoDerivs (CC BY-NC-ND) licence. This licence only allows you to download this work and share it with others as long as you credit the authors, but you can't change the article in any way or use it commercially. More information and the full terms of the licence here: https://creativecommons.org/licenses/ Takedown If you consider content in White Rose Research Online to be in breach of UK law, please notify us by emailing eprints@whiterose.ac.uk including the URL of the record and the reason for the withdrawal request. Identifying vulnerabilities and ensuring security functionality by security testing is a widely applied measure to evaluate and improve the security of software. Due to the openness of modern software-based systems, applying appropriate security testing techniques is of growing importance and essential to perform effective and efficient security testing. Therefore, an overview of actual security testing techniques is of high value both for researchers to evaluate and refine the techniques and for practitioners to apply and disseminate them. This chapter fulfills this need and provides an overview of recent security testing techniques. For this purpose, it first summarize the required background of testing and security engineering. Then, basics and recent developments of security testing techniques applied during the secure software development lifecycle, i.e., model-based security testing, code-based testing and static analysis, penetration testing and dynamic analysis, as well as security regression testing are discussed. Finally, the security testing techniques are illustrated by adopting them for an example three-tiered web-based business application.

show abstract

“…Yu et al [140] propose fault-based prioritization of test cases, which directly utilizes the knowledge of their capability to detect faults.…”

Section: Test Case Prioritizationmentioning

confidence: 99%

Security Testing

Felderer

Büchler

Johns

et al. 2016

Advances in Computers

126

View full text Add to dashboard Cite

show abstract

“…This approach focuses on not only detecting the faults but also finding out where the set of faults located in a program so as to provide ease to debugging activity. Yu et al proposed a fault based prioritization strategy for specification based testing that prioritizes the test cases based on their potential of detecting the faults [25]. The information about test cases and corresponding faults covered by them has been derived using specifications.…”

Section: Related Workmentioning

confidence: 99%

A Hybrid Approach of Clustering and Time-Aware Based Novel Test Case Prioritization Technique

Chaurasia¹,

Agarwal²

2016

IJDTA

View full text Add to dashboard Cite

show abstract

“…Many coverage-based prioritization techniques (such as [4] [5], fault severities [4], ability to detect specification-based faults [38], data from the test history [5] [9], or fault-exposing-potential [26]. The effects of granularity [23] and compositions of test suites have been reported.…”

Section: Related Workmentioning

confidence: 99%

Is XML-Based Test Case Prioritization for Validating WS-BPEL Evolution Effective in Both Average and Adverse Scenarios?

Jia

Mei

Chan

et al. 2014

2014 IEEE International Conference on Web Services

View full text Add to dashboard Cite

AbstractIn real life, a tester can only afford to apply one test case prioritization technique to one test suite against a service-oriented workflow application once in the regression testing of the application, even if it results in an adverse scenario such that the actual performance in the test session is far below the average. It is unclear whether the factors of test case prioritization techniques known to be significant in terms of average performance can be extrapolated to adverse scenarios. In this paper, we examine whether such a factor or technique may consistently affect the rate of fault detection in both the average and adverse scenarios. The factors studied include prioritization strategy, artifacts to provide coverage data, ordering direction of a strategy, and the use of executable and non-executable artifacts. The results show that only a minor portion of the 10 studied techniques, most of which are based on the iterative strategy, are consistently effective in both average and adverse scenarios. To the best of our knowledge, this paper presents the first piece of empirical evidence regarding the consistency in the effectiveness of test case prioritization techniques and factors of service-oriented workflow applications between average and adverse scenarios.

show abstract

Fault-based test suite prioritization for specification-based testing

Cited by 38 publications

References 45 publications

Security Testing

Security Testing

A Hybrid Approach of Clustering and Time-Aware Based Novel Test Case Prioritization Technique

Is XML-Based Test Case Prioritization for Validating WS-BPEL Evolution Effective in Both Average and Adverse Scenarios?

Contact Info

Product

Resources

About