specflow-skill
Generates SpecFlow BDD tests for C#/.NET with Gherkin feature files and step bindings. Use when user mentions "SpecFlow", "C# BDD", ".NET Gherkin", "[Binding]", "[Given]/[When]/[Then]". Triggers on: "SpecFlow", "C# BDD", ".NET BDD", "step bindings", "[Binding]".
- License 许可
- MIT
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- license
- MIT
- metadata
- { "author": "TestMu AI", "version": "1.0" }
- description
- Generates SpecFlow BDD tests for C#/.NET with Gherkin feature files and step bindings. Use when user mentions "SpecFlow", "C# BDD", ".NET Gherkin", "[Binding]", "[Given]/[When]/[Then]". Triggers on: "SpecFlow", "C# BDD", ".NET BDD", "step bindings", "[Binding]".
02 资源文件 2
- 参考文档reference/advanced-patterns.md2.6 KB
- 参考文档reference/playbook.md20.9 KB
03 SKILL.md 正文
SpecFlow BDD Skill
Core Patterns
Feature File (Features/Login.feature)
Feature: User Login
Scenario: Successful login
Given I am on the login page
When I enter "user@test.com" as email
And I enter "password123" as password
And I click the login button
Then I should see the dashboard
And the welcome message should contain "Welcome"
Scenario: Invalid credentials
Given I am on the login page
When I enter "wrong@test.com" as email
And I enter "wrong" as password
And I click the login button
Then I should see error "Invalid credentials"
Scenario Outline: Login with various users
Given I am on the login page
When I enter "<email>" as email
And I enter "<password>" as password
And I click the login button
Then I should see "<result>"
Examples:
| email | password | result |
| admin@test.com | admin123 | Dashboard |
| user@test.com | pass123 | Dashboard |
| bad@test.com | wrong | Error |
Step Bindings
using TechTalk.SpecFlow;
using NUnit.Framework;
[Binding]
public class LoginSteps
{
private readonly ScenarioContext _context;
private IWebDriver _driver;
public LoginSteps(ScenarioContext context)
{
_context = context;
_driver = (IWebDriver)_context["driver"];
}
[Given(@"I am on the login page")]
public void GivenIAmOnTheLoginPage()
{
_driver.Navigate().GoTo("http://localhost:3000/login");
}
[When(@"I enter ""(.*)"" as email")]
public void WhenIEnterEmail(string email)
{
_driver.FindElement(By.Id("email")).SendKeys(email);
}
[When(@"I enter ""(.*)"" as password")]
public void WhenIEnterPassword(string password)
{
_driver.FindElement(By.Id("password")).SendKeys(password);
}
[When(@"I click the login button")]
public void WhenIClickLogin()
{
_driver.FindElement(By.CssSelector("button[type='submit']")).Click();
}
[Then(@"I should see the dashboard")]
public void ThenIShouldSeeDashboard()
{
Assert.That(_driver.Url, Does.Contain("/dashboard"));
}
[Then(@"I should see error ""(.*)""")]
public void ThenIShouldSeeError(string error)
{
var element = _driver.FindElement(By.CssSelector(".error"));
Assert.That(element.Text, Does.Contain(error));
}
}
Hooks
[Binding]
public class Hooks
{
private readonly ScenarioContext _context;
public Hooks(ScenarioContext context) { _context = context; }
[BeforeScenario]
public void BeforeScenario()
{
var driver = new ChromeDriver();
_context["driver"] = driver;
}
[AfterScenario]
public void AfterScenario()
{
((IWebDriver)_context["driver"]).Quit();
}
}
Dependency Injection (Context Injection)
// SpecFlow auto-injects ScenarioContext, FeatureContext, and custom POCOs
public class LoginSteps
{
private readonly LoginPage _loginPage;
public LoginSteps(LoginPage loginPage) { _loginPage = loginPage; }
}
Setup: dotnet add package SpecFlow.NUnit or SpecFlow.xUnit
Run: dotnet test
Cloud Execution on TestMu AI
Set environment variables: LT_USERNAME, LT_ACCESS_KEY
// Hooks.cs
[BeforeScenario]
public void Setup()
{
var ltOptions = new Dictionary<string, object>
{
{ "user", Environment.GetEnvironmentVariable("LT_USERNAME") },
{ "accessKey", Environment.GetEnvironmentVariable("LT_ACCESS_KEY") },
{ "build", "SpecFlow Build" },
{ "name", ScenarioContext.Current.ScenarioInfo.Title },
{ "platformName", "Windows 11" },
{ "video", true },
{ "console", true },
};
var options = new ChromeOptions();
options.AddAdditionalOption("LT:Options", ltOptions);
_driver = new RemoteWebDriver(
new Uri("https://hub.lambdatest.com/wd/hub"), options);
}
Report: SpecFlow+ LivingDoc extension for rich HTML reports
Deep Patterns
For advanced patterns, debugging guides, CI/CD integration, and best practices,
see reference/playbook.md.
04 同仓库更多 Skills
runpodctl
Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.
runpod
Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.
runpod-usage
How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.
runpod-templates
Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.
runpod-migrate
Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.
runpod-mcp
Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.