A Construction of Fault Test Constraint Based on the Optimal Fusion Set of Multiple Slices

Article Preview

Abstract:

The standard program slicing of different slices is put into the fusion matrix of the optimal fusion to measure the consistent fusion of slices. In the biopsy of the actual fusion process, the slicing techniques with high consistent fusion and balanced fusion distribution are used to reasonably allocate each weight coefficient, and thus the final fusion estimation formula is obtained. We use slice fusion, path conditions, as well as the internal mechanism of software fault trigger and propagation, to construct the test constraint of a fault. It can help to direct high quality test case design and to evaluate the applicability of the adaptive random testing.

You might also be interested in these eBooks

Info:

Periodical:

Advanced Materials Research (Volumes 774-776)

Pages:

1604-1608

Citation:

Online since:

September 2013

Export:

Price:

Permissions CCC:

Permissions PLS:

Сopyright:

© 2013 Trans Tech Publications Ltd. All Rights Reserved

Share:

Citation:

[1] Krinke J. Slicing, chopping and path conditions with barriers. Sofeware Quality Journal, 2004, 12(4): 339-360. [doi: 10. 1023/B: SQJO. 0000039792. 93414. a5].

DOI: 10.1023/b:sqjo.0000039792.93414.a5

Google Scholar

[2] Mayer J. Adaptive random testing by bisection with restriction. In: Lau KK, Banach R, eds. Proc. of the 7th Int'l Conf. on Formal Engineering Methods(ICFEM 2005). LNCS 3785, Heidelburg: Springer-Verlag, 2005. 251-263. [doi: 10. 1007/11576280_18].

DOI: 10.1007/11576280_18

Google Scholar

[3] Chen TY, Merkel R. An upper bound on software testing effectiveness. ACM Trans. on Software Engineering and Methodology, 2008, 17(3): 1-27. [doi: 10. 1145/1363102. 1363107].

DOI: 10.1145/1363102.1363107

Google Scholar

[4] Yang GN, Feng XF, Fan LJ. Multi-Sensor Data Fusion Algorithm Based on Optimal Fusion Set. Joural of Software, 2012, 23(Suppl. (1): 134-140.

Google Scholar

[5] Sun Chang-Ai. A Constraint-Based Approach to Identifying and Analyzing Failure-Causing Regions. Joural of Software, 2012, 23(7): 1688-1701 [doi: 10. 3724/SP.J. 1001. 2012. 04126].

DOI: 10.3724/sp.j.1001.2012.04126

Google Scholar