This work benchmarks eight LLMs generating Gherkin from three requirement corpora, scoring validity, runner acceptance, judged coverage and quality, similarity to gold standard, stability, and cost, and releases the corpora, gold standard, and prototype.
Abstract
Behaviour-Driven Development (BDD) encodes acceptance criteria in Gherkin, but hand-authoring is laborious, and it is unclear which large language model (LLM) drafts it best. We benchmark eight LLMs generating Gherkin from three requirement corpora (requirement lists, user stories, RFP excerpts) over 2960 generations, scoring validity, runner acceptance, judged coverage and quality, similarity to gold standard, stability, and cost. Validity is near the ceiling, yet only 78% of outputs load in the Cucumber runner: a fifth emits several Feature blocks per file. Two student annotators (a small, non-expert panel) calibrate the judge on 72 blinded generations. Human score levels are matched (error 0.33 versus 0.35 between the humans) but outputs are ordered far less reliably (ICC 0.47 versus 0.64; coverage 0.21 versus 0.76): magnitudes hold, but fine rankings do not. Against that gold standard, models span 66–107% of the human–human ceiling, ordering differently again. Pareto analysis leaves three of eight models non-dominated: cost varies 157×, judged quality 0.36 points. Per-model prompt tuning yields no cross-validated gain; a restrictive token budget truncates verbose models. Two newer models displace the low-cost front: tier-level findings transfer, and model names are dated quickly. We release the corpora, gold standard, and prototype. Model choice should weigh cost and runner acceptance over judged quality.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.