2019
DOI: 10.32604/cmes.2019.04681
|View full text |Cite
|
Sign up to set email alerts
|

An Automated Approach to Generate Test Cases From Use Case Description Model

Abstract: Test complexity and test adequacy are frequently raised by software developers and testing agents. However, there is little research works at this aspect on specification-based testing at the use case description level. Thus, this research proposes an automatic test cases generator approach to reduce the test complexity and to enhance the percentage of test coverage. First, to support the infrastructure for performing automatic, this proposed approach refines the use cases using use case describing template an… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
8
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 8 publications
(8 citation statements)
references
References 19 publications
0
8
0
Order By: Relevance
“…According to [18] modeling speci cations can reduce the time and effort spent in test case generation, thus the use of models in the approach [13] also decreases the time and effort required by software engineers to add missing speci cations into new or existing test cases. Likewise, the approach in [14], uses a template [15] to create a complete description of use cases by including all the relevant details to eliminate manual intervention to ensure the coverage of essential requirements by test cases.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…According to [18] modeling speci cations can reduce the time and effort spent in test case generation, thus the use of models in the approach [13] also decreases the time and effort required by software engineers to add missing speci cations into new or existing test cases. Likewise, the approach in [14], uses a template [15] to create a complete description of use cases by including all the relevant details to eliminate manual intervention to ensure the coverage of essential requirements by test cases.…”
Section: Discussionmentioning
confidence: 99%
“…Manual intervention is required by the software engineer between nearly every automated step. On the contrary, the approaches proposed in [12,14] are fully automatic and do not require manual work. Nonetheless, UMTG [13] can generate test cases parallelly in a multicore platform, decreasing the performance time which would be increased due to manual intervention.…”
Section: Discussionmentioning
confidence: 99%
“…SBT is characterized by test data being generated from the specification without concerning the structure of the corresponding program and test results being analyzed based on the specification [4][5][6][7][8]. Formal specifications may allow the test data generation and test result analysis to be done rigorously, systematically, and even automatically in many cases [9][10][11][12]. In our work, we mainly use formal specifications in pre-and postconditions, such as Vienna Development Method (VDM) [13], a formal method that has been developed over past years [14,15], and Structured-Object-Oriented Formal Language (SOFL) [16], which has the potential of practical use in industry and serves as a solid foundation to develop a method of functional scenario-based test data generation [17].…”
Section: Introductionmentioning
confidence: 99%
“…Many research works had employed the heuristic search algorithms to propose an approach to generate or to prioritize the regression test cases [2,8,14,24,18,19].…”
Section: Introductionmentioning
confidence: 99%
“…Alrawashed et al [2] developed an automated approach for test suite optimization. In their approach, they generated test cases from the use case description model.…”
Section: Introductionmentioning
confidence: 99%