tetianna
Community@tetianna
Playwright end-to-end testing skills for the Didaxis platform, covering Gherkin test design, CI failure triage, accessibility scans, and Jira bug reporting.
Agent Skills by tetianna
Showing 11 vetted skills indexed across 1 GitHub repositories.
tetiannajira-ticket-to-gherkin
Generates Gherkin test scenarios from Jira ticket acceptance criteria via the Atlassian MCP.
tetiannapom-conventions
Enforces Page Object Model conventions for Playwright tests against the Didaxis UI.
tetiannanetwork-mocked-edge-cases
Writes deterministic Playwright edge-case tests for the programs flow using page.route network mocks.
tetiannaexplore-and-generate
Explores a live UI to find untested user flows and outputs a Gherkin test plan.
tetiannajira-bug-reporter
Analyzes Playwright test failures and creates Jira bug sub-tasks with attached screenshots.
tetiannaci-failure-triage
Diagnoses failed GitHub Actions Playwright runs and posts structured root-cause reports to pull requests.
tetiannadidaxis-bulk-cleanup
Deletes all Didaxis Studio programs via REST API after a dry-run confirmation.
tetiannaa11y-checks
Adds axe-core accessibility scans and keyboard navigation coverage to Playwright UI tests.
tetiannaself-heal
Repairs drifted Playwright locators in page object models after triage confirms test issues.
tetiannaexploratory-charter
Formats a feature and risk hypothesis into an exploratory testing charter and findings template.
tetiannaplaywright-test-cleanup
Enforces API-based cleanup of test data created by Playwright tests in Didaxis.
Frequently Asked Questions About tetianna
FAQPage SchemaWhat tasks can I accomplish with tetianna's testing skills?▼
You can convert Jira tickets into Gherkin scenarios, generate Playwright tests following Page Object Model conventions, mock network edge cases, add axe-core accessibility scans, triage failing CI runs, heal drifted locators, file Jira bug reports, and clean up Didaxis test data via the REST API.
Who are these skills designed for?▼
QA engineers, SDETs, and developers maintaining Playwright end-to-end suites for the Didaxis UI. They suit teams practicing BDD with Gherkin, enforcing Page Object Model conventions, and needing structured CI failure triage and exploratory testing charters.
How do the CI failure triage and self-heal skills work together?▼
When a build goes red, ci-failure-triage pulls logs and the playwright-report artifact via gh cli, classifies the failure as a real app bug or test drift, and posts a diagnosis to the PR. If drift is confirmed, self-heal fixes the broken locator; app bugs route to jira-bug-reporter instead.
What prerequisites and dependencies do these skills require?▼
A Playwright test suite against the Didaxis platform, access to Jira for ticket and bug operations, the gh cli for fetching CI run logs and artifacts, @axe-core/playwright for accessibility scans, and the Didaxis REST API (GET /api/programs) for bulk program cleanup.
Can these skills discover test coverage gaps without a Jira ticket?▼
Yes. The explore-and-generate skill explores a live UI for untested user flows and outputs a Gherkin test plan when no ticket exists. It is explicitly reserved for ticketless coverage discovery; when a ticket exists, jira-ticket-to-gherkin is used instead.