2017 IEEE International Conference on Software Testing, Verification and Validation (ICST) 2017
DOI: 10.1109/icst.2017.58
|View full text |Cite
|
Sign up to set email alerts
|

Test Design as Code: JCUnit

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(3 citation statements)
references
References 6 publications
0
3
0
Order By: Relevance
“…Given that both ACTS and PICT have their own limitations in constraint definition, we introduced a new tool in our previous work Ukai (2007) .…”
Section: Background and Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Given that both ACTS and PICT have their own limitations in constraint definition, we introduced a new tool in our previous work Ukai (2007) .…”
Section: Background and Related Workmentioning
confidence: 99%
“…Minimizing changes is important because the output, which represents a test suite, sometimes contains fundamental parameters that are expensive to control such as OS or filesystem to be used in test execution. Popular tools for CIT such as ACTS ( Kuhn, Kacker & Lei, 2008 ), PICT ( Czerwonka, 2006 ), and JCUnit ( Ukai 2007 ) can add parameters not presented in an initial covering array and generate an output as by assigning values to them so that the combinations between the values of the given parameters and the existing ones are covered. However, this limits reuse of only one covering array.…”
Section: Background and Related Workmentioning
confidence: 99%
See 1 more Smart Citation