NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
A Flutter package for Behavior-Driven Development (BDD) testing.
Latest stable
2.0.0
Last release 4 days ago
18 Nov 2026
Release timing varies
gaps range from 3 weeks to 11 months
Nearly every release is documented
notes for 12 of 12 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
14 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
2.0 changes the shape of the generated code. Run dart run bdd_flutter migrate once to move a 1.x project; see "Upgrading from 1.x" in the README.
2.0 changes the shape of the generated code. Run dart run bdd_flutter migrate once to move a 1.x project; see "Upgrading from 1.x" in the README.
.bdd_scenarios.dart (one class per scenario, edited by you and appended to by the tool) to three files per feature:
<name>.bdd_steps.dart: a generated abstract interface class <Feature>StepsContract, rewritten on every build<name>_steps.dart: your <Feature>Steps implements <Feature>StepsContract, created once and never touched again<name>.bdd_test.dart: the generated testsI add 2 "apple" is iAdd(num number, String text) instead of iAdd2Apple(). Steps that differ only in these values share a methodnum when every value is a number Dart prints back unchanged, bool for true/false, otherwise StringWidgetTester through a tester field set by the generated test, not as a method parameterUnimplementedError instead of passing silentlycucumber_gherkin).bdd_flutter/manifest.yaml), incremental append and build --force; build always rewrites generated files and never touches yoursdart test tag names, such as 1.x's @className("X"), are ignoredscenario_suffix is replaced by steps_suffix (default Steps); scenario_suffix is only read by migrate. additional_imports now go into new _steps.dart files.feature files are parsed by the official cucumber_gherkin parser and mapped from cucumber_messages types (#6)But and * steps, Scenario Outline, Rule (with its own Background), several Examples blocks, several tags on one line, comments, escaped \| in tables and non-English keywords (# language: fr)Rule: blocks become group('Rule: …'), and a Rule's Background runs after the feature'sString docString and List<List<String>> dataTable, with <column> placeholders filled per rowtest()/testWidgets() as tags:, merged from feature, rule, scenario and Examples; build lists them for dart_test.yaml@skip on a feature, rule, scenario or Examples block generates skip: truegenerate_widget_tests now applies to scenarios without @unitTest/@widgetTest; the closest decorator wins (scenario, then rule, then feature)dart format, using your package's style and page widthbuild reports steps your _steps.dart lacks and steps it overrides that the feature no longer hasmigrate command carries 1.x step code into the new steps filesmixin SharedSteps (test/shared_steps.dart), created with stubs the first time steps are shared and then yours. New steps classes mix it in. A step becoming shared later only prints a tip, and method names are worked out per feature, so a change to one feature never breaks anotherbdd_flutter test report: Scenario Outline rows and Rules are nested, skipped tests are shown and counted, failures point at the line in your steps file, features are sorted by path, durations appear only for failed and slow tests, and colors follow NO_COLOR and the terminalIncrémenter → Incrementer, Vietnamese included); text with no Latin letters gets a stable hashed name. No extra dependency: the folding table is built in. Names never collide with Dart keywords or Object members.feature files are reported with line and column and skipped; build exits with code 1 so CI catches themkeywordType (context, action, outcome, conjunction)' or $ no longer produce invalid code, in arguments and test names1.50, 02134 or $10.00 are never turned into a different valuelogin.feature is a real widget test with mocktailtest/cart/cart.feature (Rule, two Examples blocks, But and *), test/compteur/compteur.feature (French keywords) and test/stress/stress.feature (doc strings, data tables, repeated placeholders, tags on Examples, symbols in step text)dart_test.yaml declaring the example's tagstest/complex/complex1.feature is marked @skip: it shows generated names for long, real-world step textYour coding agent can read these notes before it upgrades. Set up the MCP server →
A beta of 2.0: please try it, including migrate on a 1.x project, and report anything odd, especially generated names. Naming rules, file names and th
A beta of 2.0: please try it, including migrate on a 1.x project, and report anything odd, especially generated names. Naming rules, file names and the contract shape can still change until 2.0.0; after that, changing them would break your steps files.
2.0 changes the shape of the generated code. Run dart run bdd_flutter migrate once to move a 1.x project; see "Upgrading from 1.x" in the README.
.bdd_scenarios.dart (one class per scenario, edited by you and appended to by the tool) to three files per feature:
<name>.bdd_steps.dart: a generated abstract interface class <Feature>StepsContract, rewritten on every build<name>_steps.dart: your <Feature>Steps implements <Feature>StepsContract, created once and never touched again<name>.bdd_test.dart: the generated testsI add 2 "apple" is iAdd(num number, String text) instead of iAdd2Apple(). Steps that differ only in these values share a methodnum when every value is a number Dart prints back unchanged, bool for true/false, otherwise StringWidgetTester through a tester field set by the generated test, not as a method parameterUnimplementedError instead of passing silentlycucumber_gherkin).bdd_flutter/manifest.yaml), incremental append and build --force; build always rewrites generated files and never touches yoursdart test tag names, such as 1.x's @className("X"), are ignoredscenario_suffix is replaced by steps_suffix (default Steps); scenario_suffix is only read by migrate. additional_imports now go into new _steps.dart files.feature files are parsed by the official cucumber_gherkin parser and mapped from cucumber_messages types (#6)But and * steps, Scenario Outline, Rule (with its own Background), several Examples blocks, several tags on one line, comments, escaped \| in tables and non-English keywords (# language: fr)Rule: blocks become group('Rule: …'), and a Rule's Background runs after the feature'sString docString and List<List<String>> dataTable, with <column> placeholders filled per rowtest()/testWidgets() as tags:, merged from feature, rule, scenario and Examples; build lists them for dart_test.yaml@skip on a feature, rule, scenario or Examples block generates skip: truegenerate_widget_tests now applies to scenarios without @unitTest/@widgetTest; the closest decorator wins (scenario, then rule, then feature)dart format, using your package's style and page widthbuild reports steps your _steps.dart lacks and steps it overrides that the feature no longer hasmigrate command carries 1.x step code into the new steps filesmixin SharedSteps (test/shared_steps.dart), created with stubs the first time steps are shared and then yours. New steps classes mix it in. A step becoming shared later only prints a tip, and method names are worked out per feature, so a change to one feature never breaks anotherbdd_flutter test report: Scenario Outline rows and Rules are nested, skipped tests are shown and counted, failures point at the line in your steps file, features are sorted by path, durations appear only for failed and slow tests, and colors follow NO_COLOR and the terminalIncrémenter → Incrementer, Vietnamese included); text with no Latin letters gets a stable hashed name. No extra dependency: the folding table is built in. Names never collide with Dart keywords or Object members.feature files are reported with line and column and skipped; build exits with code 1 so CI catches themkeywordType (context, action, outcome, conjunction)' or $ no longer produce invalid code, in arguments and test names1.50, 02134 or $10.00 are never turned into a different valuelogin.feature is a real widget test with mocktailtest/cart/cart.feature (Rule, two Examples blocks, But and *), test/compteur/compteur.feature (French keywords) and test/stress/stress.feature (doc strings, data tables, repeated placeholders, tags on Examples, symbols in step text)dart_test.yaml declaring the example's tagstest/complex/complex1.feature is marked @skip: it shows generated names for long, real-world step textdart run bdd_flutter test now runs all test files (BDD and regular), not just .bdd_test.dart
dart run bdd_flutter test now runs all test files (BDD and regular), not just .bdd_test.dartBDDController incremental build (rename, remove, modify, delete, force, append scenarios)Fix class name generation for names starting with digits (e.g., "123 login" → X123LoginScenario)
"123 login" → X123LoginScenario)snakeCaseToCamelCase crash on leading/trailing underscoresUnnamed, unnamed, step) instead of empty strings for edge cases"Form auto-save") produced invalid Dart class namesStringX extensions (PascalCase, snakeCaseToCamelCase, toSnakeCase)Step.methodName edge cases (digits, special chars, empty text, params)Scenario class name generation, decorator resolution, and hash consistencyDecorator parsing and set helpersRemoved build_runner dependency entirely — use dart run bdd_flutter build instead
build_runner dependency entirely — use dart run bdd_flutter build instead--no-widget-test and --new-only CLI flagsbuild.yaml to .bdd_flutter/config.yaml.bdd_scenarios.g.dart to .bdd_scenarios.dart and .bdd_test.g.dart to .bdd_test.dartdart run bdd_flutter build and dart run bdd_flutter test--force flag to regenerate all filestest command with formatted Feature/Scenario report outputtest_dir config optionscenario_suffix config option (e.g., Steps instead of Scenario)additional_imports config option@unitTest / @widgetTest decorators at feature and scenario levellate fields for shared state)change output files extension to .bdd_scenarios.g.dart and .bdd_test.g.dart
.bdd_scenarios.g.dart and .bdd_test.g.dartignore_features option to build.yaml- fix import file name
add ignore decorator on feature
fix builder issue with examples
add @disableReporter and @enableReporter decorators
@disableReporter and @enableReporter decorators- add @className decorator - fix build_runner error
@className decoratorrefactor to use factory pattern
- Initial release
One column per month.