Wiki support for automated definition of software test cases

Abstract

Purpose The design of tests is a very important step in the software development process because it allows us to match the users’ expectations with the finished product. Considered as a cumbersome activity, efforts have been made to automatize and alleviate the burden of test generation, but it is still a largely neglected step. The study aims to propose taking advantage of existing requirement artifacts, like scenarios that describe the dynamic of the domain in a very early stage of software development, to obtain tests from them. Design/methodology/approach In particular, the approach proposed complement the scenarios that are textually described with a glossary, the language extended lexicon. Thus, a set of rules to derive tests from scenarios is also proposed. The tests are then described using the task/method model. Findings The main findings of this study consist of an extension of a previously presented set of rules. And, a tool based on a media wiki platform that makes possible to record scenarios and the language extended lexicon and implement the rules to obtain the tests. Originality/value The main originality of this study is the glossary which complements scenarios, the semantic support to obtain tests and the tool to automatize the approach.

Embedded software test case design based on black box technology

“…Boundary value analysis is a test case design method for black box testing. It uses the boundary values of input data as the basis for test case design to discover defects in software systems [20]. The basic idea of boundary value analysis method is to divide the input data into multiple intervals and select the boundary value of each interval as a test case to test the behavior of the system at the boundary value.…”

User acceptance test for software development in the agricultural domain using natural language processing

“…The Task/Method model is a conceptual model where knowledge is described in declarative form. This facilitates their processing by execution engines and planners (Antonelli et al, 2018). A conceptual model is composed of two sub-models: a domain model and a reasoning model (Adla et al, 2007;Schreiber et al, 1999;Trichet & Tchounikine, 1999).…”

AGUTER a platform for automated generation of user acceptance tests from requirements specifications

“…This section describes the proposed rules for translating scenarios into a conceptual model (tasks and methods). These rules have already been presented in previous works (Antonelli et al, 2018(Antonelli et al, , 2020, so only a summary is described here.…”

“…This section describes the proposed rules for translating scenarios into a conceptual model (tasks and methods). These rules have already been presented in previous works (Antonelli et al , 2018, 2020), so only a summary is described here. Rule 1 (Tasks identification): In the scenario model, each verb in the scenario's episodes is translated into a task in task/method model. Each scenario title is also a task in task/method model.…”