Przejdź do treści
Biblioteka skilli
Programowanie · Testowanie

bmad-testarch-framework

/bmad-testarch-framework

Inicjuje framework testowy z Playwright lub Cypress w projekcie.

Licencja
MIT
Ostatnia zmiana repozytorium
06.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
76
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: resources/hooks/tea-enforce.cjs

Co robi i kiedy

Inicjuje framework testowy z Playwright lub Cypress w projekcie.

Wyzwalacze z opisu

lets setup test framework
Oryginalny opis (EN)

Initialize test framework with Playwright or Cypress. Use when the user says "lets setup test framework" or "I want to initialize testing framework

Jak działa

  1. Conventions
  2. On Activation
  3. Workflow Architecture
  4. Initialization Sequence
Sekcje z nagłówków SKILL.md, w oryginale · 82 linii, 424 słów
Podgląd SKILL.md
---
name: bmad-testarch-framework
description: 'Initialize test framework with Playwright or Cypress. Use when the user says "lets setup test framework" or "I want to initialize testing framework"'
---

# Test Framework Setup

**Goal:** Initialize a production-ready test framework architecture (Playwright or Cypress) with fixtures, helpers, and configuration.

**Role:** You are the Master Test Architect.

You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.

## Conventions

- Bare paths (e.g. `instructions.md`) resolve from the skill root.
- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).
- `{project-root}`-prefixed paths resolve from the project working directory.
- `{skill-name}` resolves to the skill directory's basename.
- Resolve sibling workflow files such as `instructions.md`, `checklist.md`, `steps-c/...`, `steps-e/...`, `steps-v/...`, and templates from `{skill-root}`.

## On Activation

### Step 1: Resolve the Workflow Block

Run: `uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow`

**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

1. `{skill-root}/customize.toml` — defaults
2. `{project-root}/_bmad/custom/{skill-name}.toml` — team overrides
3. `{project-root}/_bmad/custom/{skill-name}.user.toml` — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.

### Step 2: Execute Prepend Steps

Execute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.

### Step 3: Load Persistent Facts

Treat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs resolved from `{project-root}` — expand them and load every matching file in lexical path order as facts. All other entries are facts verbatim.

### Step 4: Load Config

Load config from `{project-root}/_bmad/tea/config.yaml` and resolve:

- `user_name`
- `communication_language`

### Step 5: Greet the User

Greet `{user_name}`, speaking in `{communication_language}`.

### Step 6: Execute Append Steps

Execute each entry in `{workflow.activation_steps_append}` in order.

Activation is complete. Begin the workflow below.

## Workflow Architecture

This workflow uses **tri-modal step-file architecture**:

- **Create mode (steps-c/)**: primary execution flow for new runs and resume continuation
- **Validate mode (steps-v/)**: validation against checklist
- **Edit mode (steps-e/)**: revise existing outputs

## Initialization Sequence

### 1. Mode Determination

"Welcome to the workflow. What would you like to do?"

- **[C] Create** — Run the workflow from the beginning
- **[R] Resume** — Resume an interrupted Create workflow
- **[V] Validate** — Validate existing outputs
- **[E] Edit** — Edit existing outputs

### 2. Route to First Step

- **If C:** Load `{skill-root}/steps-c/step-01-preflight.md`
- **If R:** Load `{skill-root}/steps-c/step-01b-resume.md` (Create-mode continuation)
- **If V:** Load `{skill-root}/steps-v/step-01-validate.md`
- **If E:** Load `{skill-root}/steps-e/step-01-assess.md`
Pliki w paczce (76)
  • SKILL.md 3 KB
  • checklist.md 14 KB
  • customize.toml 1 KB
  • instructions.md 1 KB
  • workflow.yaml 2 KB
  • resources/framework-setup-progress.example.md 11 KB
  • resources/tea-index.csv 16 KB
  • resources/hooks/tea-enforce.cjs 40 KB
  • resources/knowledge/adr-quality-readiness-checklist.md 25 KB
  • resources/knowledge/api-request.md 17 KB
  • resources/knowledge/api-testing-patterns.md 27 KB
  • resources/knowledge/auth-session.md 16 KB
  • resources/knowledge/burn-in.md 6 KB
  • resources/knowledge/ci-burn-in.md 22 KB
  • resources/knowledge/component-tdd.md 18 KB
  • resources/knowledge/confidence-gate.md 4 KB
  • resources/knowledge/contract-testing.md 41 KB
  • resources/knowledge/data-factories.md 17 KB
  • resources/knowledge/email-auth.md 24 KB
  • resources/knowledge/error-handling.md 22 KB
  • resources/knowledge/evidence-integrity.md 25 KB
  • resources/knowledge/feature-flags.md 23 KB
  • resources/knowledge/file-utils.md 13 KB
  • resources/knowledge/fixture-architecture.md 12 KB
  • resources/knowledge/fixtures-composition.md 11 KB
  • resources/knowledge/intercept-network-call.md 13 KB
  • resources/knowledge/library-integration-mandate.md 8 KB
  • resources/knowledge/log.md 11 KB
  • resources/knowledge/maestro-flows.md 29 KB
  • resources/knowledge/mobile-ci-device-lab.md 35 KB
  • resources/knowledge/mobile-test-strategy.md 14 KB
  • resources/knowledge/network-error-monitor.md 12 KB
  • resources/knowledge/network-first.md 16 KB
  • resources/knowledge/network-recorder.md 15 KB
  • resources/knowledge/nfr-criteria.md 26 KB
  • resources/knowledge/overview.md 10 KB
  • resources/knowledge/pact-broker-webhooks.md 15 KB
  • resources/knowledge/pact-consumer-di.md 12 KB
  • resources/knowledge/pact-consumer-framework-setup.md 36 KB
  • resources/knowledge/pact-mcp.md 11 KB
  • resources/knowledge/pactjs-utils-consumer-helpers.md 16 KB
  • resources/knowledge/pactjs-utils-mandate.md 16 KB
  • resources/knowledge/pactjs-utils-overview.md 12 KB
  • resources/knowledge/pactjs-utils-provider-verifier.md 22 KB
  • resources/knowledge/pactjs-utils-request-filter.md 7 KB
  • resources/knowledge/pactjs-utils-zod-to-pact.md 12 KB
  • resources/knowledge/playwright-cli.md 15 KB
  • resources/knowledge/playwright-config.md 21 KB
  • resources/knowledge/playwright-utils-mandate.md 13 KB
  • resources/knowledge/probability-impact.md 19 KB
  • resources/knowledge/recurse.md 13 KB
  • resources/knowledge/risk-governance.md 21 KB
  • resources/knowledge/selective-testing.md 21 KB
  • resources/knowledge/selector-resilience.md 19 KB
  • resources/knowledge/test-healing-patterns.md 21 KB
  • resources/knowledge/test-levels-framework.md 14 KB
  • resources/knowledge/test-priorities-matrix.md 12 KB
  • resources/knowledge/test-quality.md 34 KB
  • resources/knowledge/timing-debugging.md 18 KB
  • resources/knowledge/visual-debugging.md 17 KB
  • resources/knowledge/webhook-module-setup.md 6 KB
  • resources/knowledge/webhook-providers.md 6 KB
  • resources/knowledge/webhook-risk-guidance.md 6 KB
  • resources/knowledge/webhook-template-matchers.md 6 KB
  • resources/knowledge/webhook-testing-fundamentals.md 3 KB
  • resources/knowledge/webhook-timeout-error.md 6 KB
  • resources/knowledge/webhook-waiting-querying.md 7 KB
  • steps-c/step-01-preflight.md 5 KB
  • steps-c/step-01b-resume.md 4 KB
  • steps-c/step-02-select-framework.md 4 KB
  • steps-c/step-03-scaffold-framework.md 26 KB
  • steps-c/step-04-docs-and-scripts.md 10 KB
  • steps-c/step-05-validate-and-summary.md 2 KB
  • steps-e/step-01-assess.md 1 KB
  • steps-e/step-02-apply-edit.md 1 KB
  • steps-v/step-01-validate.md 4 KB

Wersje

W bazie nie ma innych skilli o nazwie bmad-testarch-framework.

Migawka bazy z 13.11.2026 · wersja paczki 9257e4092d84 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100bmad-tea-framework
    Inicjuje framework testowy oraz konfigurację CI/CD dla stosów przeglądarkowych, backendowych i mobilnych.
  • 90bmad-testarch-test-review
    Ocenia jakość testów według dobrych praktyk i wskazuje, co poprawić.
  • 90bmad-testarch-test-design
    Tworzy plany testów na poziomie systemu lub epiku oraz strategię testowania.
  • 100gds-test-framework
    Inicjalizuje framework testowy gier dla Unity, Unreal lub Godot.
  • 90test-framework-migration-skill
    Migruje i konwertuje skrypty automatyzacji testów między Selenium, Playwright, Puppeteer i Cypress, w dowolnym kierunku, na przykład z Selenium na Playwright.
  • 100cypress-expert
    Pomaga w pracy z Cypress: własne polecenia, fixtures, wtyczki, testy wizualne i testy komponentów oraz struktura testów.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.