Published: March 22, 2013
Author(s)
Richard Kuhn (NIST), Itzel Dominguez Mendoza (Centro Nacional de Metrologia), Raghu Kacker (NIST), Yu Lei (UTA)
Conference
Name: Second International Workshop on Combinatorial Testing 2013 (IWCT 2013)
Dates: March 18-22, 2013
Location: Luxembourg, Luxembourg
Citation: Proceedings of the IEEE Sixth International Conference on Software Testing, Verification and Validation Workshops (ICSTW 2013), pp. 352-361
Announcement
Combinatorial testing applies factor covering arrays to test all t-way combinations of input or configuration state space. In some testing situations, it is not practical to use covering arrays, but any set of tests covers at least some portion of t-way combinations up to t <= n. This report describes measures of combinatorial coverage that can be used in evaluating the degree of t-way coverage of any test suite, regardless of whether it was initially constructed for combinatorial coverage.
Combinatorial testing applies factor covering arrays to test all t-way combinations of input or configuration state space. In some testing situations, it is not practical to use covering arrays, but any set of tests covers at least some portion of t-way combinations up to t <= n. This report...
See full abstract
Combinatorial testing applies factor covering arrays to test all t-way combinations of input or configuration state space. In some testing situations, it is not practical to use covering arrays, but any set of tests covers at least some portion of t-way combinations up to t <= n. This report describes measures of combinatorial coverage that can be used in evaluating the degree of t-way coverage of any test suite, regardless of whether it was initially constructed for combinatorial coverage.
Hide full abstract
Keywords
component; combinatorial testing; factor covering array; configuration model; state-space coverage; verification and validation (V&; V); t-way testing; null
Control Families
None selected
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
