Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

open-testing-convert-specflow

Étoiles13

Forks1

Mis à jour20 avril 2026 à 12:49

Convert SpecFlow (.NET / C# BDD) and Reqnroll (SpecFlow 4.x successor) test suites — `.feature` files, `[Binding]` step definitions with `[Given]` / `[When]` / `[Then]`, `ScenarioContext` / `FeatureContext` state sharing, hooks `[BeforeScenario]` / `[AfterScenario]` / `[BeforeFeature]` / `[BeforeTestRun]` / `[BeforeStep]` with tag filters, `specflow.json` config, Cucumber expressions `{string}` / `{int}` and regex matchers, `[StepArgumentTransformation]`, SpecFlow.Assist `CreateInstance` / `CreateSet`, DI via `IObjectContainer`, `[Scope]`, `ScenarioOutline` with `Examples`, `Rule`, tables, doc strings, MSTest / NUnit / xUnit runners, SpecFlow+LivingDoc. Targets: Selenium, Playwright, Cypress, Cucumber, Appium, Behave, Eggplant, OpenTest.AI, Testers.AI. MANDATORY TRIGGERS: "convert SpecFlow", "SpecFlow to <target>", ".NET BDD", "[Binding]", "ScenarioContext", "Reqnroll".

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

AgenticTesting

AgenticTesting/OpenTestingAI

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

open-testing-coverage

AgenticTesting/OpenTestingAI

Test coverage analysis, gap detection, coverage reporting, and coverage optimization using the COVERED agent pipeline. Use this skill whenever the user mentions test coverage, coverage analysis, coverage gaps, traceability matrix, coverage heat map, coverage dashboard, coverage metrics, coverage trends, test intensity, risk-based coverage, requirement coverage, code coverage mapping, or wants to know if their testing is sufficient. Also trigger when users ask about uncovered requirements, orphaned tests, coverage regression, or coverage targets. MANDATORY TRIGGERS: coverage, traceability, gap analysis, RTM, heat map, coverage dashboard, coverage trend, test intensity evaluation.

2026-05-1413

open-testing-create

AgenticTesting/OpenTestingAI

Generate concrete test cases, test data, and test scripts from a test design technique and context. Applies 106 test design techniques (boundary value analysis, equivalence partitioning, decision tables, state transitions, pairwise, combinatorial, etc.) to enumerate test conditions and author realistic test cases with inputs, expected results, and traceability. Use this skill whenever the user needs to: create test cases from a technique, apply a testing method to requirements, generate test data, design test scenarios, or populate test scripts. Triggers include: 'test cases', 'create tests', 'test design', 'apply [technique name]', 'generate test data', 'test scenarios', or any technique name (BVA, EP, combinatorial, etc.).technique name (BVA, EP, combinatorial, etc.).

2026-05-1413

open-testing-design

AgenticTesting/OpenTestingAI

Generate comprehensive test strategies, quality engineering approaches, risk analysis, and optimal technique selection. Use this when you need to develop test strategies, perform quality risk analysis, select test design techniques, assess testability, estimate test effort, define governance structures, or establish test exit criteria and coverage targets.

2026-05-1413

open-testing-management

AgenticTesting/OpenTestingAI

Test management, defect management, process evaluation, and maturity assessment using the MANAGES agent pipeline. Use this skill whenever the user mentions test management, defect management, process improvement, TMMi, maturity assessment, ARCI matrix, quality policy, test policy, process evaluation, defect lifecycle, triage, test process, roles and responsibilities, QAM, QPM, GTA, generic test agreements, process maturity, test improvement, or wants to evaluate and improve their testing practices. Also trigger for defect tracking, anomaly management, process compliance, test governance, or organizational testing capability. MANDATORY TRIGGERS: test management, defect management, TMMi, maturity, ARCI, process improvement, quality policy, defect lifecycle, process evaluation, test governance.

2026-05-1413

open-testing-plan

AgenticTesting/OpenTestingAI

Generate comprehensive test plans, schedules, resource allocation, environment setup, and test data strategies. Use this when you need to develop master test plans, level-specific test plans, allocate resources and environments, plan non-functional testing, define end-to-end testing chains, or establish test data management strategies.

2026-05-1413

open-testing-reporting

AgenticTesting/OpenTestingAI

Test reporting, progress dashboards, release advice, and final test reports using the REPORTS agent pipeline. Use this skill whenever the user mentions test report, progress report, test dashboard, release advice, go/no-go decision, test metrics, defect trends, test execution summary, quality assessment, final test report, lessons learned, RAG status, or wants to generate any kind of testing status or quality report. Also trigger for executive summaries, sprint test reports, release readiness, or stakeholder communication about testing. MANDATORY TRIGGERS: test report, progress, dashboard, release advice, go/no-go, test metrics, defect trend, RAG status, quality report, test summary

2026-05-1413

name	open-testing-convert-specflow
description	Convert SpecFlow (.NET / C# BDD) and Reqnroll (SpecFlow 4.x successor) test suites — `.feature` files, `[Binding]` step definitions with `[Given]` / `[When]` / `[Then]`, `ScenarioContext` / `FeatureContext` state sharing, hooks `[BeforeScenario]` / `[AfterScenario]` / `[BeforeFeature]` / `[BeforeTestRun]` / `[BeforeStep]` with tag filters, `specflow.json` config, Cucumber expressions `{string}` / `{int}` and regex matchers, `[StepArgumentTransformation]`, SpecFlow.Assist `CreateInstance` / `CreateSet`, DI via `IObjectContainer`, `[Scope]`, `ScenarioOutline` with `Examples`, `Rule`, tables, doc strings, MSTest / NUnit / xUnit runners, SpecFlow+LivingDoc. Targets: Selenium, Playwright, Cypress, Cucumber, Appium, Behave, Eggplant, OpenTest.AI, Testers.AI. MANDATORY TRIGGERS: "convert SpecFlow", "SpecFlow to <target>", ".NET BDD", "[Binding]", "ScenarioContext", "Reqnroll".
license	MIT
metadata	{"family":"open-testing-convert","source":"specflow","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","testcafe","nightwatch","codeceptjs","taiko","protractor","katalon","playwright-bdd","behave","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — SpecFlow (and Reqnroll)

Converts SpecFlow (.NET / C# BDD) suites to any supported target, and emits SpecFlow from any source. Reqnroll (the 2024+ fork / successor) is handled by the same skill — syntax is identical, only namespaces differ (Reqnroll replaces TechTalk.SpecFlow).

When to use

Trigger when any of these signals are present in the repo:

.feature files sitting alongside C# projects (.csproj).
SpecFlow, SpecFlow.NUnit, SpecFlow.xUnit, SpecFlow.MsTest, SpecFlow.Tools.MsBuild.Generation, Reqnroll, Reqnroll.NUnit, Reqnroll.xUnit, Reqnroll.MsTest NuGet PackageReference entries.
C# files with [Binding] class attribute and any of [Given("...")], [When("...")], [Then("...")], [StepDefinition("...")] method attributes.
using TechTalk.SpecFlow; or using Reqnroll; imports.
specflow.json or reqnroll.json config file.
App.config with <specFlow> section (legacy).
.feature.cs auto-generated code-behind files (these are artefacts — ignore on extraction, regenerate on emission).
ScenarioContext.Current, FeatureContext.Current, ScenarioContext["key"] indexer use.
[BeforeScenario], [AfterScenario], [BeforeFeature], [AfterFeature], [BeforeTestRun], [AfterTestRun], [BeforeStep], [AfterStep], [BeforeScenarioBlock], [AfterScenarioBlock] attributes.
[StepArgumentTransformation] methods.
SpecFlow.Assist extension method calls (table.CreateInstance<T>(), table.CreateSet<T>()).
[Scope(Tag="…")], [Scope(Feature="…")], [Scope(Scenario="…")] attributes.

How to use

Read the master orchestrator (open-testing-convert/SKILL.md).
Read this skill's reference files in order: source-profile.md, extraction.md, mappings.md.
Read the target primer for your target.
Emit per target Emission Checklist.

Scope

SpecFlow 3.x (3.9+), SpecFlow 4.x (where it exists), and Reqnroll 1.x / 2.x (successor project — forward-compatible treatment).
Gherkin .feature files (Cucumber-compatible subset with Rule, Background, Scenario Outline, Examples, tags, data tables, doc strings).
Step definitions in any C# namespace with [Binding] marker and step attributes.
Parameter matchers: Cucumber expressions ({string}, {int}, {float}, {word}) and regex (@"..." raw strings).
[StepArgumentTransformation] custom converters (with optional regex pattern).
All hook attributes including tag-filtered variants ([BeforeScenario("@web")]).
[Scope]-restricted bindings (tag / feature / scenario).
Context injection via constructor parameters (SpecFlow DI).
Plugin DI: Boo.Di (default), SpecFlow.Autofac, SpecFlow.Microsoft.Extensions.DependencyInjection.
SpecFlow.Assist table assist extensions: CreateInstance<T>, CreateSet<T>, CompareToInstance<T>, CompareToSet<T>.
Test runners: NUnit, xUnit, MSTest (affects attribute emission in code-behind only; SpecFlow layer is runner-agnostic for extraction).
External data: [Scope] + .feature @DataTable links, SpecFlow+ExternalData (CSV/Excel via @DataSource on scenarios).
Common drivers in step bodies: Selenium .NET bindings, Playwright for .NET, RestSharp, HttpClient, FlaUI (desktop — flag), Coypu (Selenium wrapper).
LivingDoc generation (livingdoc.json → HTML) — metadata only; not part of canonical.

Out of scope

Xamarin.UITest or Appium .NET bindings used inside step bodies — preserve verbatim with todo kind + warning.
SpecFlow+Runner (deprecated; supply-chain removed 2022) — flag for replacement with NUnit/xUnit/MSTest runner.
SpecFlow.Actions.* plugins (Selenium/Playwright/Browserstack helpers) — map to direct driver calls where unambiguous, else preserve as todo.
Legacy SpecFlow 2.x / 1.x syntax differences — flag but attempt best-effort.
MsBuild-time code-behind generation internals — regenerate on emission, ignore on extraction.

Quick reference

SpecFlow	Canonical	Example target
`[Binding] public class LoginSteps { … }`	step def class inlining	preserved in `step_defs` with class grouping
`[Given(@"I am on the login page")]`	step def registration with matcher_mode: "regex"	Cucumber-compatible pattern on target
`[Given("I am on the login page")]`	step def registration with matcher_mode: "cucumber_expr"	same
`driver.Navigate().GoToUrl(url)`	`{kind: "navigate", url}`	Playwright `page.goto(url)`
`driver.FindElement(By.Id("email")).SendKeys(text)`	`{kind: "input", locator: {strategy: "id", value: "email"}, value: text}`
`ScenarioContext["token"] = x` / `ScenarioContext["token"]`	state_ref into `scenario_state.token`	per-target world/state slot
`[BeforeScenario("@api")]`	hook with `tag_filter: ["@api"]`	before-tag hook on target
`[StepArgumentTransformation]`	`parameter_types` entry	Cucumber `defineParameterType` / `ParameterType`
`table.CreateInstance<User>()`	`data_table_binding: {type: "User", shape: "single"}`	per-target data table helper
`[Scope(Tag="web")]`	class-level `tag_filter: ["@web"]` on each step def	filter at registration time
`Examples:`	`data_driven: {rows, iterations}`	expanded or preserved per target

See reference/mappings.md for the full cookbook.