behave-skill — Claude Code skill for Behave tests
Generate Python BDD tests with Gherkin feature files and Behave step implementations. Useful when you need to turn user flows into runnable scenarios.
MIT 227 installs ★ 393 updated 2026-10-13
npx skills add LambdaTest/agent-skills --skill behave-skill -a claude-codeWhat behave-skill does
The skill helps create Gherkin feature files and Python steps for Behave. Its examples cover login scenarios, data tables, tagged test runs, and environment hooks. A failed scenario can also trigger a screenshot.
The browser examples use behave and selenium; install them with pip install behave selenium. Run tests with behave, or write a JSON report with behave --format json -o report.json. The TestMu AI setup reads LT_USERNAME and LT_ACCESS_KEY, so that cloud configuration depends on those environment variables.
The reference/playbook.md file includes project setup, Page Objects, test data, and a GitHub Actions example. It also covers API steps, but you still need to define steps that match your application’s behavior.
What it helps with
- write Gherkin scenarios for a user flow
- connect scenario steps to browser actions
- test varied inputs with a Scenario Outline
- run selected scenarios by tag
- capture a screenshot when a scenario fails
Example prompts for the agent
- Create a Gherkin feature file and Python Behave steps for the login flow.
- Add a Scenario Outline to test several sets of credentials.
- Set up a hook that captures a screenshot when a scenario fails.
How to install behave-skill
1Skills CLI (Vercel)
npx skills add LambdaTest/agent-skills --skill behave-skill -a claude-code2Manually: put the files in place
~/.claude/skills/behave-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/behave-skill/
1Skills CLI (Vercel)
npx skills add LambdaTest/agent-skills --skill behave-skill -a codex2Manually: put the files in place
.agents/skills/behave-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add LambdaTest/agent-skills --skill behave-skill -a cursor2Manually: put the files in place
.cursor/skills/behave-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install LambdaTest/agent-skills behave-skill2Manually: put the files in place
.github/skills/behave-skill/SKILL.md1Skills CLI (Vercel)
npx skills add LambdaTest/agent-skills --skill behave-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/LambdaTest/agent-skills --path behave-skillManually: put the files in place
.devin/skills/behave-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add LambdaTest/agent-skills --skill behave-skill -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about behave-skill
How do I install behave-skill in Claude Code?
Run npx skills add LambdaTest/agent-skills --skill behave-skill -a claude-code. The skill file is placed at ~/.claude/skills/behave-skill/SKILL.md.
What does behave-skill do?
It helps generate Python BDD tests: Gherkin feature files and step implementations for Behave. The examples also cover environment hooks and running tests by tag.
What do I need for the browser test examples?
Install behave and selenium with pip install behave selenium. The TestMu AI cloud setup also requires LT_USERNAME and LT_ACCESS_KEY.
Source text
SKILL.md · MIT
---
name: behave-skill
description: >
Generates Behave BDD tests for Python with Gherkin feature files and step
implementations. Use when user mentions "Behave", "Python BDD", "Python
Gherkin". Triggers on: "Behave", "Python BDD", "behave test", "Python
feature file".
languages:
- Python
category: bdd-testing
license: MIT
metadata:
author: TestMu AI
version: "1.0"
---
# Behave BDD Skill
## Core Patterns
### Feature File (features/login.feature)
```gherkin
Feature: User Login
As a registered user
I want to log into the application
Background:
Given I am on the login page
Scenario: Successful login
When I enter "[email protected]" as email
And I enter "password123" as password
And I click login
Then I should see the dashboard
And the welcome message should say "Welcome"
Scenario: Invalid credentials
When I enter "[email protected]" as email
And I enter "wrong" as password
And I click login
Then I should see error "Invalid credentials"
Scenario Outline: Login with various users
When I enter "<email>" as email
And I enter "<password>" as password
And I click login
Then I should see "<result>"
Examples:
| email | password | result |
| [email protected] | admin123 | Dashboard |
| [email protected] | wrong | Error |
```
### Step Definitions (features/steps/login_steps.py)
```python
from behave import given, when, then
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
@given('I am on the login page')
def step_on_login(context):
context.browser.get(context.base_url + '/login')
@when('I enter "{text}" as email')
def step_enter_email(context, text):
el = context.browser.find_element(By.ID, 'email')
el.clear()
el.send_keys(text)
@when('I enter "{text}" as password')
def step_enter_password(context, text):
el = context.browser.find_element(By.ID, 'password')
el.clear()
el.send_keys(text)
@when('I click login')
def step_click_login(context):
context.browser.find_element(By.CSS_SELECTOR, 'button[type="submit"]').click()
@then('I should see the dashboard')
def step_see_dashboard(context):
WebDriverWait(context.browser, 10).until(
EC.url_contains('/dashboard')
)
assert '/dashboard' in context.browser.current_url
@then('I should see error "{msg}"')
def step_see_error(context, msg):
error = WebDriverWait(context.browser, 5).until(
EC.visibility_of_element_located((By.CSS_SELECTOR, '.error'))
)
assert msg in error.text
```
### Environment Hooks (features/environment.py)
```python
from selenium import webdriver
def before_all(context):
context.base_url = 'http://localhost:3000'
def before_scenario(context, scenario):
context.browser = webdriver.Chrome()
context.browser.implicitly_wait(10)
def after_scenario(context, scenario):
if scenario.status == 'failed':
context.browser.save_screenshot(f'screenshots/{scenario.name}.png')
context.browser.quit()
```
### Tags
```gherkin
@smoke
Feature: Login
@critical
Scenario: ...
```
```bash
behave --tags=@smoke
behave --tags="@smoke and not @slow"
```
## Setup: `pip install behave selenium`
## Run: `behave` or `behave features/login.feature`
### Cloud Execution on TestMu AI
Set environment variables: `LT_USERNAME`, `LT_ACCESS_KEY`
```python
# environment.py
from selenium import webdriver
import os
def before_scenario(context, scenario):
lt_options = {
"user": os.environ["LT_USERNAME"],
"accessKey": os.environ["LT_ACCESS_KEY"],
"build": "Behave Build",
"name": scenario.name,
"platformName": "Windows 11",
"video": True,
"console": True,
"network": True,
}
options = webdriver.ChromeOptions()
options.set_capability("LT:Options", lt_options)
context.driver = webdriver.Remote(
command_executor=f"https://{os.environ['LT_USERNAME']}:{os.environ['LT_ACCESS_KEY']}@hub.lambdatest.com/wd/hub",
options=options,
)
```
## Report: `behave --format json -o report.json`
## Deep Patterns
See `reference/playbook.md` for production-grade patterns:
| Section | What You Get |
|---------|-------------|
| §1 Project Setup | behave.ini, project structure, dependencies |
| §2 Feature Files | Gherkin with Scenario Outline, data tables, Background |
| §3 Step Definitions | Type registration, API steps, common steps with PyHamcrest |
| §4 Environment Hooks | before_all/scenario/feature, screenshot on failure, DB isolation |
| §5 Page Objects | BasePage with waits, LoginPage, reusable components |
| §6 Fixtures & Test Data | DatabaseHelper, transaction rollback, JSON data loader |
| §7 LambdaTest Integration | Remote browser creation, cloud capabilities |
| §8 CI/CD Integration | GitHub Actions with Postgres, Selenium, Allure reports |
| §9 Debugging Table | 12 common problems with causes and fixes |
| §10 Best Practices | 14-item BDD testing checklist |
© TestMu AI · MIT · LambdaTest/agent-skills