2017
DOI: 10.1063/1.5005458
|View full text |Cite
|
Sign up to set email alerts
|

Coverage criteria for test case generation using UML state chart diagram

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
1
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 26 publications
0
1
0
Order By: Relevance
“…These unimportant features are usually redundant and can add noise to the classifier's design. As a result, it's important to select data with useful characteristics that will help classifier performance improve [9][10][11].…”
Section: Introductionmentioning
confidence: 99%
“…These unimportant features are usually redundant and can add noise to the classifier's design. As a result, it's important to select data with useful characteristics that will help classifier performance improve [9][10][11].…”
Section: Introductionmentioning
confidence: 99%
“…In software testing, genetic algorithms (GAs) have successfully achieved the maximum coverage criterion in object-oriented classes [1][2][3][4]. The coverage criterion is a definition for which parts of the program are to be executed and whether the set of test cases can be executed as defined [5,6]. There are a variety of coverage criteria for testing (e.g., branch, line, mutation).…”
Section: Introductionmentioning
confidence: 99%