2016 13th International Joint Conference on Computer Science and Software Engineering (JCSSE) 2016
DOI: 10.1109/jcsse.2016.7748881
|View full text |Cite
|
Sign up to set email alerts
|

A tool for constrained pairwise test case generation using statistical user profile based prioritization

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
2
2

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 8 publications
0
5
0
Order By: Relevance
“…Given an invalid test case, a straightforward approach of replacing it is to clone this test case. In each clone, the parameters involved in constraints are changed to new values that do not violate constraints, and the number of clones is chosen to preserve coverage [6], [40], [84], [85], [86]. Another attempt is to first remove invalid test cases and then use a genetic algorithm to add some feasible ones [83].…”
Section: Replacementioning
confidence: 99%
“…Given an invalid test case, a straightforward approach of replacing it is to clone this test case. In each clone, the parameters involved in constraints are changed to new values that do not violate constraints, and the number of clones is chosen to preserve coverage [6], [40], [84], [85], [86]. Another attempt is to first remove invalid test cases and then use a genetic algorithm to add some feasible ones [83].…”
Section: Replacementioning
confidence: 99%
“…In software testing, some combinations between input parameters and parameter values are commonly infeasible and unachievable in practice for executing in the SUT which will yield expensively false positives. Moreover, the pairwise testing technique does not provide a solution for handling the constraints between input parameters and parameter values, the testers have to review the test cases from pairwise testing and delete invalid test cases manually themselves [19]. For example from Table 1, consider that Internet Explorer cannot be executed on Mac OS so the operating system must not be Mac OS.…”
Section: Constraint Handlingmentioning
confidence: 99%
“…Constraints can be set as a form of logical expressions and rules. The logical expression and rules define a condition that must be achieved by every test case and must be performed correctness checking during test case generation whether a combination of identified parameters and parameter values or a test case violates the constraints or not [3,4,23]. The form of logical expression and rule can be converted from one to another as shown in Table 2.…”
Section: Constraints Modelingmentioning
confidence: 99%
See 2 more Smart Citations