Vansah

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.

Ideal for Selenium, REST-assured, JUnit/TestNG projects

Repo: <code>vansah-cucumber-java</code> (example integration)

- Works with Maven/Gradle setups
- Ideal for Selenium, REST-assured, JUnit/TestNG projects
- Repo: <code>vansah-cucumber-java</code> (example integration)

Download: GitHub - Cucumber Java Integration

___________________________________________________________

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.

<code>@TC-&lt;TEST_CASE_KEY&gt;</code> Examples:

- <code>@TC-&lt;TEST_CASE_KEY&gt;</code> Examples:
- <code>@TC-PROJ-C1</code>
- <code>@TC-QA-102</code>

You execute via your usual pipeline (local, CI, scheduled runs).

Optional evidence (screenshots/attachments)

Optional run metadata (environment, sprint, release, build, etc.)

- Scenario result (pass/fail/skip)
- Optional step-level outcomes
- Optional evidence (screenshots/attachments)
- Optional run metadata (environment, sprint, release, build, etc.)

A Vansah Connect token for API authentication

Network access from your runner/CI to your Jira/Vansah instance (as required)

- 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)

Use one consistent configuration pattern across languages:

<code>VANSAH_CONNECT_TOKEN</code> (or your token variable name)

<code>JIRA_PROJECT_KEY</code> (or Vansah project key / mapping)

<code>VANSAH_BASE_URL</code> (if applicable to your deployment)

- <code>VANSAH_CONNECT_TOKEN</code> (or your token variable name)
- <code>JIRA_PROJECT_KEY</code> (or Vansah project key / mapping)
- <code>VANSAH_BASE_URL</code> (if applicable to your deployment)

<code>ENVIRONMENT_NAME</code> (e.g., Staging / Prod)

<code>BUILD_NUMBER</code> / <code>CI_RUN_ID</code>

- <code>ENVIRONMENT_NAME</code> (e.g., Staging / Prod)
- <code>RELEASE_NAME</code> (e.g., 1.12.0)
- <code>SPRINT_NAME</code>
- <code>BUILD_NUMBER</code> / <code>CI_RUN_ID</code>

Tip: standardize your variable names across integrations so your CI templates are reusable.

Add the Vansah integration dependency to your project (Maven/Gradle)

Configure environment variables or <code>.env</code>

- Add the Vansah integration dependency to your project (Maven/Gradle)
- Configure environment variables or <code>.env</code>

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

Set <code>ENVIRONMENT_NAME</code>, <code>RELEASE_NAME</code>, <code>BUILD_NUMBER</code> in pipeline variables

- Store token in secrets
- Set <code>ENVIRONMENT_NAME</code>, <code>RELEASE_NAME</code>, <code>BUILD_NUMBER</code> in pipeline variables

Vansah Cucumber Integration

Trust, Security and Privacy

Home

Community

Contact

Find answers and get help from Intercom Support and Community Experts

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Link, Press control-option-right-arrow to exit

Empty Help Center

Uh oh. That page doesn’t exist.

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

Capability	What you get	Typical toggle
Scenario-level reporting	One result per scenario	Default
Step-level reporting	Each step outcome captured	`STEP_LEVEL_REPORTING=true`
Evidence on failure	Screenshot/attachment on fail	`SCREENSHOT_ON_FAILURE=true`
Test plan association	Results grouped under a plan	`STANDARD_TEST_PLAN_KEY` / `ADVANCED_TEST_PLAN_KEY`
Folder / suite mapping	Runs organized in Vansah folders	`TEST_FOLDER_PATH`
Issue linkage	Results linked to Jira issues	`JIRA_ISSUE_KEY`
Run metadata	Sprint/Release/Environment included	`SPRINT_NAME`, etc.

Vansah Cucumber Integration

Supported Cucumber Integrations

Java (Cucumber JVM)

Other languages (coming soon)

How it works (same for all languages)

1) Map Cucumber scenarios to Vansah test cases

2) Run tests normally

3) Sync results to Vansah automatically

Common setup (applies to every language)

Prerequisites

Required configuration

Feature matrix (enable per language)

Language-specific sections

Java (Cucumber JVM)

Install

Tagging

Run

Recommended CI usage