CucumberCommand class

Runs integration tests using Cucumber/Gherkin feature files.

The CucumberCommand generates and executes integration tests from .feature files written in Gherkin syntax. It supports device targeting, flavor-specific testing, and generates HTML reports for test results.

Usage

Run all feature tests:

morpheme cucumber

Run specific feature tests:

morpheme cucumber login,checkout

Run with specific flavor:

morpheme cucumber --flavor production

Run on specific device:

morpheme cucumber --device-id emulator-5554

Options

• --flavor: Target environment flavor (default: dev)
• --morpheme-yaml: Path to morpheme.yaml configuration
• --generate-l10n: Generate localization files before testing
• --device-id: Target device identifier for testing

Feature Files

Tests are discovered from integration_test/features/*.feature files. Each .feature file should contain Gherkin scenarios describing the integration test behavior.

Report Generation

• Generates NDJSON output for test processing
• Creates HTML reports when npm is available
• Reports are saved to integration_test/report/

Dependencies

• Requires gherkin command-line tool
• Uses Flutter integration test framework
• Optional: npm for HTML report generation
• Requires valid morpheme.yaml configuration

Exceptions

Throws ProcessException if gherkin tool is not found. Throws FileSystemException if feature files are missing. Throws TestFailureException if integration tests fail.