2012 IEEE Fifth International Conference on Software Testing, Verification and Validation 2012
DOI: 10.1109/icst.2012.164
|View full text |Cite
|
Sign up to set email alerts
|

Dependency-Based Test Case Selection and Prioritization in Embedded Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
3
3
3

Relationship

0
9

Authors

Journals

citations
Cited by 13 publications
(8 citation statements)
references
References 12 publications
0
8
0
Order By: Relevance
“…in [4]. The proposed method in [4] is applicable for the componentbased systems and the dependencies can be identified through analyzing system structure, architecture, and requirements.…”
Section: Inputmentioning
confidence: 99%
“…in [4]. The proposed method in [4] is applicable for the componentbased systems and the dependencies can be identified through analyzing system structure, architecture, and requirements.…”
Section: Inputmentioning
confidence: 99%
“…Caliebe et al [30] present an approach based on dependencies between components whereby analysis could be performed on a graph representation of such dependencies. Two applications of their proposed approach are possible: general test case selection and test case prioritization for regression testing.…”
Section: Related Workmentioning
confidence: 99%
“…Several works use this model for selecting regression integration tests [113]- [115]. Other works do not rely on this notation, but create their own formalized model from it, such as the Component Dependency Model [116], or directly specify needed dependencies within a formal description language, such as the Specification Description Language (SDL) [117]. These models focus on relevant dependencies and allow automatic analysis, e.g.…”
Section: Traceability Based Ciamentioning
confidence: 99%
“…For regression testing of single units, other specification models are needed, as no information about behavior is stored within class diagrams or other structural models. Several works identify suitable models for defining behavior, such as the UML Sequence Diagram [116], [113], Extended Finite State Machines (EFSM) [118] or the SDL [117]. Again, identification of influences of changes is conducted using change classes, which define whether a test case is influenced or not.…”
Section: Traceability Based Ciamentioning
confidence: 99%