vividus

Scaffold Vividus BDD projects with plugins and .story files.

18|9|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill vividus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vividus
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/vividus
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill vividus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Vividus BDD story authorship is error-prone because step phrasing, parameter syntax, configuration structure, and plugin selection must match the framework exactly.

Core Features & Use Cases

  • Guided Vividus setup: Helps you bootstrap a BOM-pinned Vividus project, including required build-system setup and conventional directories for stories and step composites.
  • Plugin-aware scaffolding: Shows how to add the correct Vividus plugins for web, REST, mobile, DB, and visual testing so the step library you write actually exists at runtime.
  • Story authoring with guardrails: Reinforces exact step wording rules (including backticks for parameters) and configuration axes (suites, profiles, environments) to avoid “pending steps” and misrouted runs.

Use Case: Create a new Vividus project for a web + REST test suite, add the needed plugins, scaffold a web smoke story and a REST smoke story, then run stories with the correct suite/profile/environment properties.

Quick Start

Use the vividus skill to generate a Vividus test plan for a new web and REST project, including which plugins to add and how to scaffold the first two .story files.

Frequently Asked Questions about vividus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Vividus BDD test automation project from scratch?

To set up a Vividus BDD test automation project, bootstrap a BOM-pinned build with Gradle, configure conventional directories for stories and step composites, and select the required plugins for your target testing layers like web or REST.

How do I write JBehave .story files without getting pending step errors?

To avoid pending step errors in JBehave .story files, use exact step phrasing and apply backtick rules for parameters. Following BDD story conventions ensures the Vividus framework recognizes and executes your steps at runtime.

What plugins do I need to add to Vividus for web and REST test automation?

For web and REST test automation in Vividus, add the specific web and REST plugins to your build. This plugin-aware scaffolding ensures the step library you author in your BDD stories actually exists and executes during runtime.

How do I configure Vividus suites, profiles, and environments for test execution?

Configure Vividus suites, profiles, and environments by setting specific properties files in your project. This configuration axis directs story execution routing and ensures your BDD stories run under the correct environment variables.

Does Vividus test automation require a specific JDK version?

Yes, Vividus test automation assumes JDK 21 for project setup and execution. Ensuring your environment matches this JDK requirement prevents build failures and compatibility issues when running BDD stories.

Why are my Vividus BDD story steps failing due to parameter syntax mistakes?

Vividus BDD story steps fail due to parameter syntax mistakes when backtick parameter rules and variable expression syntax are not followed exactly. Using references-backed troubleshooting prevents hallucinated step phrasings and syntax errors.