Sync Cucumber automation results into Vansah Test Management for Jira.
Keep execution evidence, step outcomes, and run metadata aligned to your Jira-based QA governance.
Supported Cucumber Integrations
Java (Cucumber JVM)
Works with Maven/Gradle setups
Ideal for Selenium, REST-assured, JUnit/TestNG projects
Repo:
vansah-cucumber-java(example integration)
Other languages (coming soon)
How it works (same for all languages)
1) Map Cucumber scenarios to Vansah test cases
You tag each scenario with a Vansah Test Case Key so Vansah knows where to post results.
Recommended tag format
@TC-<TEST_CASE_KEY>
Examples:@TC-PROJ-C1@TC-QA-102
2) Run tests normally
You execute via your usual pipeline (local, CI, scheduled runs).
3) Sync results to Vansah automatically
During execution, the integration posts:
Scenario result (pass/fail/skip)
Optional step-level outcomes
Optional evidence (screenshots/attachments)
Optional run metadata (environment, sprint, release, build, etc.)
Common setup (applies to every language)
Prerequisites
Vansah installed in your Jira site
A Vansah Connect token for API authentication
Network access from your runner/CI to your Jira/Vansah instance (as required)
Required configuration
Use one consistent configuration pattern across languages:
Required
VANSAH_CONNECT_TOKEN(or your token variable name)JIRA_PROJECT_KEY(or Vansah project key / mapping)VANSAH_BASE_URL(if applicable to your deployment)
Optional (recommended)
ENVIRONMENT_NAME(e.g., Staging / Prod)RELEASE_NAME(e.g., 1.12.0)SPRINT_NAMEBUILD_NUMBER/CI_RUN_ID
Tip: standardize your variable names across integrations so your CI templates are reusable.
Feature matrix (enable per language)
Capability | What you get | Typical toggle |
Scenario-level reporting | One result per scenario | Default |
Step-level reporting | Each step outcome captured |
|
Evidence on failure | Screenshot/attachment on fail |
|
Test plan association | Results grouped under a plan |
|
Folder / suite mapping | Runs organized in Vansah folders |
|
Issue linkage | Results linked to Jira issues |
|
Run metadata | Sprint/Release/Environment included |
|
Language-specific sections
Java (Cucumber JVM)
Install
Add the Vansah integration dependency to your project (Maven/Gradle)
Configure environment variables or
.env
Tagging
Add the Vansah tag directly to scenarios:
@TC-PROJ-C1 Scenario: Successful login Given I am on the login page When I enter valid credentials Then I should see the dashboard
Run
mvn clean test
Recommended CI usage
Store token in secrets
Set
ENVIRONMENT_NAME,RELEASE_NAME,BUILD_NUMBERin pipeline variables