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

SAGA Toolbox: Interactive Testing of Guarded Assertions

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
2
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 10 publications
0
4
0
Order By: Relevance
“…A lot of existing research has been devoted to automated testing, such as automatic generation of test cases, test scripts, etc from NL requirements or restricted requirements [11] [12] [13] [14]. However, none of these tasks can guarantee correct results, and some require manual addition of files or manual intervention to get the correct results.…”
Section: Related Workmentioning
confidence: 99%
“…A lot of existing research has been devoted to automated testing, such as automatic generation of test cases, test scripts, etc from NL requirements or restricted requirements [11] [12] [13] [14]. However, none of these tasks can guarantee correct results, and some require manual addition of files or manual intervention to get the correct results.…”
Section: Related Workmentioning
confidence: 99%
“…The SAGA approach [14] is used to express such guarded assertions. The SAGA approach is supported by a tool chain consisting of an interactive test case editor as well as a description language (i.e., the T-EARS language).…”
Section: Guarded Assertions T-ears and The Saga Tool Chainmentioning
confidence: 99%
“…Another approach is to start from the point of the domain knowledge of the tester, trying to simplify the specification language itself so it can be used by the average tester. While many such attempts use a graphical representation of the language [11], the SAGA 1 [14] approach instead offers interactive visual feedback while writing the test cases with a minimal textual specification language. The approach starts close to the domain knowledge of the test engineers with the goal of allowing the testers (and the requirements engineers) to think of the system as they are used to, without the burden of mastering temporal logic languages.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation