On the Understanding of BDD Scenarios’ Quality: Preliminary Practitioners’ Opinions

Oliveira, Gabriel; Marczak, Sabrina

doi:10.1007/978-3-319-77243-1_18

Cited by 6 publications

(6 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We could see in our data that one participant who did not trust the completeness of the feature file validated his answer using the step code and source code. Our study complements the study by Oliveira and Marczak [34] on the importance of conforming to quality guidelines in formulating feature files.…”

Section: Discussion and Limitations Of Study Resultssupporting

confidence: 55%

“…Moreover, one participant pointed out that a scenario described in one of the feature files had a pre-condition which did not have a corresponding implementation in the source code. Such an issue has been described in [34] as a consequence of adding unnecessary detail to a feature file. Completeness of a feature file is an attribute that practitioners found to be important for a feature file [34].…”

Section: Discussion and Limitations Of Study Resultsmentioning

confidence: 99%

“…Such an issue has been described in [34] as a consequence of adding unnecessary detail to a feature file. Completeness of a feature file is an attribute that practitioners found to be important for a feature file [34]. We could see in our data that one participant who did not trust the completeness of the feature file validated his answer using the step code and source code.…”

Section: Discussion and Limitations Of Study Resultsmentioning

confidence: 99%

See 2 more Smart Citations

Mining reading patterns from eye-tracking data: method and demonstration

et al. 2019

View full text Add to dashboard Cite

Understanding how developers interact with different software artifacts when performing comprehension tasks has a potential to improve developers' productivity. In this paper, we propose a method to analyze eye-tracking data using process mining to find distinct reading patterns of how developers interacted with the different artifacts. To validate our approach, we conducted an exploratory study using eyetracking involving 11 participants. We applied our method to investigate how developers interact with different artifacts during domain and code understanding tasks. To contextualize the reading patterns and to better understand the perceived benefits and challenges participants associated with the different artifacts and their choice of reading patterns, we complemented the eye-tracking data with the data obtained from think aloud. The study used behavior driven development (BDD), a development practice that is increasingly used in Agile software development contexts, as a setting. The study shows that our method can be used to explore developers' behavior at an aggregated level and identify behavioral patterns at varying levels of granularity.

show abstract

Section: Discussion and Limitations Of Study Resultssupporting

confidence: 55%

Section: Discussion and Limitations Of Study Resultsmentioning

confidence: 99%

Section: Discussion and Limitations Of Study Resultsmentioning

confidence: 99%

See 1 more Smart Citation

Mining reading patterns from eye-tracking data: method and demonstration

et al. 2019

View full text Add to dashboard Cite

show abstract

“…BDD scenarios specify the expected software behaviour through a set of plain English textual steps written using the Gherkin syntax [4]. The relatively unconstrained format of such specifications, however, gives rise to most of the problems typically found in natural language requirements specifications such as verbosity, incompleteness, and ambiguity [5], which often make them difficult to understand and assess [6]. Furthermore, poorly-written BDD scenarios has been reported in the literature as one of the key hindrances to achieve the benefits of the approach [7].…”

Section: Introductionmentioning

confidence: 99%

Towards a Domain-Specific Language for Behaviour-Driven Development

Silva

2023

2023 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)

View full text Add to dashboard Cite

This paper introduces a high-level domain-specific language (DSL) and its rich editing environment to allow the specification of consistent and testable Behaviour-Driven Development (BDD) scenarios as user requirements at different levels of abstraction. We preliminary evaluated our approach by looking at its potential to support the writing of BDD scenarios in five open-source projects on GitHub. Results have shown the language was able to fully support, with minor adaptations, the specification of consistent user requirements, allowing also a complete mapping between domain and interactive behaviours through BDD scenarios.

show abstract

“…BDD stories specify the expected software behaviour through a set of natural language textual scenarios describing transitions on a state machine. However, as there is no guidance regarding the vocabulary that should be used to describe the expected software behaviour into the stories, most of the issues related to natural language requirements specifications such as verbosity, incompleteness, and ambiguity still persist [24].…”

Section: Introductionmentioning

confidence: 99%

Towards a Domain-Specific Language to Specify Interaction Scenarios for Web-Based Graphical User Interfaces

Silva

2022

Companion of the 2022 ACM SIGCHI Symposium on Engineering Interactive Computing Systems

View full text Add to dashboard Cite

The communication gap between software developers and subjectmatter experts is one of the foremost long-standing problems in software development. The level of formality of the user requirements specification has a strong impact on the ability of these two groups to communicate effectively. Domain-Specific Languages (DSLs) are seen as one of the potential solutions to address this issue by raising the abstraction level of the software specification while keeping the necessary formalism to allow for software analysis, design, and verification. This paper discusses the ongoing development of a high-level DSL and its rich editing environment to allow the specification of consistent and testable interaction scenarios as user requirements for web-based graphical user interfaces. The language grammar has been developed based on the Gherkin syntax that supports Behaviour-Driven Development (BDD). Results of a preliminary evaluation regarding the consistency of actions and states of interaction elements specified for web user interfaces showed that the grammar is able to support a consistent specification of BDD scenarios as user requirements at the interaction level. CCS CONCEPTS• Software and its engineering → Domain specific languages; • Human-centered computing → Interactive systems and tools.

show abstract

On the Understanding of BDD Scenarios’ Quality: Preliminary Practitioners’ Opinions

Cited by 6 publications

References 5 publications

Mining reading patterns from eye-tracking data: method and demonstration

Mining reading patterns from eye-tracking data: method and demonstration

Towards a Domain-Specific Language for Behaviour-Driven Development

Towards a Domain-Specific Language to Specify Interaction Scenarios for Web-Based Graphical User Interfaces

Contact Info

Product

Resources

About