Boundary Coverage Criteria for Test Generation from Formal Models

Test Case Generation Based on State and Activity Models.

“…Kosmatov et al [12] developed a novel methodology to generate test cases automatically from a given set of test conditions and the input domain. Their approach mainly performs a boundary value analysis on discrete neighborhood of input values and then uses a cost minimization function in the domain to generate test cases automatically.…”

Boundary Value Testing Using Integrated Circuit Fault Detection Rule

“…Philip proposed a boundary test cases generation method based on UML state chart specifications [24]. Nikolai defined a family of model-based coverage criteria based on formalizing boundary-value testing heuristics [16].…”

“…There are a large number of test cases generation strategies, such as random testing [4,8], equivalence partitioning [1,23], boundary value testing [9,16,22], path testing [15,8], and domain testing [12,29].…”

Quality of Automatically Generated Test Cases based on OCL Expressions

“…In order to quantify the quality of test sets, coverage criteria are necessary [5,11,14]. There are many widely approved coverage criteria, each of which is focused on certain aspects of the specification or the SUT.…”

“…Whereas most coverage criteria have been defined and investigated in the area of code-based test generation, we focus on coverage of the specification. We investigate coverage criteria that either focus on conditions [5] or partition boundaries [11,12] of the specification. To combine the advantages of both kind of criteria, we also define new coverage criteria.…”