testeiya 0.10.0 → 0.10.2

package/skills/playwright/playwright-cli/references/tracing.md

@@ -1,139 +0,0 @@
-# Tracing
-
-Capture detailed execution traces for debugging and analysis. Traces include DOM snapshots, screenshots, network activity, and console logs.
-
-## Basic Usage
-
-```bash
-# Start trace recording
-playwright-cli tracing-start
-
-# Perform actions
-playwright-cli open https://example.com
-playwright-cli click e1
-playwright-cli fill e2 "test"
-
-# Stop trace recording
-playwright-cli tracing-stop
-```
-
-## Trace Output Files
-
-When you start tracing, Playwright creates a `.playwright-cli/traces/` directory with several files:
-
-### `trace-{timestamp}.trace`
-
-**Action log** - The main trace file containing:
-- Every action performed (clicks, fills, navigations)
-- DOM snapshots before and after each action
-- Screenshots at each step
-- Timing information
-- Console messages
-- Source locations
-
-### `trace-{timestamp}.network`
-
-**Network log** - Complete network activity:
-- All HTTP requests and responses
-- Request headers and bodies
-- Response headers and bodies
-- Timing (DNS, connect, TLS, TTFB, download)
-- Resource sizes
-- Failed requests and errors
-
-### `resources/`
-
-**Resources directory** - Cached resources:
-- Images, fonts, stylesheets, scripts
-- Response bodies for replay
-- Assets needed to reconstruct page state
-
-## What Traces Capture
-
-| Category | Details |
-|----------|---------|
-| **Actions** | Clicks, fills, hovers, keyboard input, navigations |
-| **DOM** | Full DOM snapshot before/after each action |
-| **Screenshots** | Visual state at each step |
-| **Network** | All requests, responses, headers, bodies, timing |
-| **Console** | All console.log, warn, error messages |
-| **Timing** | Precise timing for each operation |
-
-## Use Cases
-
-### Debugging Failed Actions
-
-```bash
-playwright-cli tracing-start
-playwright-cli open https://app.example.com
-
-# This click fails - why?
-playwright-cli click e5
-
-playwright-cli tracing-stop
-# Open trace to see DOM state when click was attempted
-```
-
-### Analyzing Performance
-
-```bash
-playwright-cli tracing-start
-playwright-cli open https://slow-site.com
-playwright-cli tracing-stop
-
-# View network waterfall to identify slow resources
-```
-
-### Capturing Evidence
-
-```bash
-# Record a complete user flow for documentation
-playwright-cli tracing-start
-
-playwright-cli open https://app.example.com/checkout
-playwright-cli fill e1 "4111111111111111"
-playwright-cli fill e2 "12/25"
-playwright-cli fill e3 "123"
-playwright-cli click e4
-
-playwright-cli tracing-stop
-# Trace shows exact sequence of events
-```
-
-## Trace vs Video vs Screenshot
-
-| Feature | Trace | Video | Screenshot |
-|---------|-------|-------|------------|
-| **Format** | .trace file | .webm video | .png/.jpeg image |
-| **DOM inspection** | Yes | No | No |
-| **Network details** | Yes | No | No |
-| **Step-by-step replay** | Yes | Continuous | Single frame |
-| **File size** | Medium | Large | Small |
-| **Best for** | Debugging | Demos | Quick capture |
-
-## Best Practices
-
-### 1. Start Tracing Before the Problem
-
-```bash
-# Trace the entire flow, not just the failing step
-playwright-cli tracing-start
-playwright-cli open https://example.com
-# ... all steps leading to the issue ...
-playwright-cli tracing-stop
-```
-
-### 2. Clean Up Old Traces
-
-Traces can consume significant disk space:
-
-```bash
-# Remove traces older than 7 days
-find .playwright-cli/traces -mtime +7 -delete
-```
-
-## Limitations
-
-- Traces add overhead to automation
-- Large traces can consume significant disk space
-- Some dynamic content may not replay perfectly

package/skills/playwright/playwright-cli/references/video-recording.md

@@ -1,216 +0,0 @@
-# Video Recording
-
-Capture browser automation sessions as video for debugging, documentation, or verification. Produces WebM (VP8/VP9 codec).
-
-## Basic Recording
-
-```bash
-# Open browser first
-playwright-cli open
-
-# Start recording, --cursor renders an animated mouse cursor that travels to each action point
-# and paces actions by 800ms so that it has time to travel
-playwright-cli video-start demo.webm --cursor --fps=60
-
-# Add a chapter marker for section transitions
-playwright-cli video-chapter "Getting Started" --description="Opening the homepage" --duration=2000
-
-# Navigate and perform actions
-playwright-cli goto https://example.com
-playwright-cli snapshot
-playwright-cli click e1
-
-# Add another chapter
-playwright-cli video-chapter "Filling Form" --description="Entering test data" --duration=2000
-playwright-cli fill e2 "test input"
-
-# Stop and save
-playwright-cli video-stop
-```
-
-## Cursor, Target Highlight and Click Point
-
-Three decorations can be drawn for each action: the mouse **cursor**, a **highlight** box around the
-target element and a **point** marker at the click point. A **title** callout naming the action comes
-with `video-show-actions`. The cursor is the only one `video-start --cursor` turns on; the rest are
-opt-in and styled with plain CSS declarations, so they look exactly the way you want.
-
-```bash
-# Cursor only, nothing else on screen
-playwright-cli video-start demo.webm --cursor
-
-# Action callout, plus a red click point and a dark frame around the target
-playwright-cli video-show-actions --duration=800 --position=top-right \
-  --point-style="width: 20px; height: 20px; border-radius: 50%; background: rgba(255,0,0,.7)" \
-  --highlight-style="outline: 2px solid #333; background: rgba(0,128,255,.15)" \
-  --title-style="font-size: 16px"
-
-# Stop annotating actions
-playwright-cli video-hide-actions
-```
-
-The same options are available programmatically, which is the better choice for hero scripts:
-
-```js
-await page.screencast.showActions({
-  // 'pointer' (default) animates the cursor from the previous action point, 'none' hides it.
-  cursor: 'pointer',
-  // How long decorations stay on screen. Actions are paced by this delay, 500ms by default.
-  duration: 800,
-  // Where the action title goes: top-left, top, top-right, bottom-left, bottom, bottom-right.
-  position: 'top-right',
-  style: {
-    // Marker at the click point. The element is zero-sized and centered on the point,
-    // so give it a size, or draw around the point with box-shadow. Hidden when omitted.
-    point: 'width: 20px; height: 20px; border-radius: 50%; background: rgba(255, 0, 0, .7)',
-    // Box that covers the target element. Hidden when omitted.
-    // Prefer `outline` over `border`, it does not shrink the box.
-    highlight: 'outline: 2px solid #333; background: rgba(0, 128, 255, .15)',
-    // The action title. Use 'display: none' to keep the cursor but drop the callout.
-    title: 'font-size: 16px',
-  },
-});
-```
-
-Notes:
-- All decorations fade out over `duration`. Override `animation` in a style to do something else.
-- The cursor stays on screen at the last action point between actions and across navigations,
-  and travels along a slightly curved path, so it reads as a hand moving a mouse.
-- Call `page.screencast.hideActions()` to stop annotating and hide the cursor.
-
-## Best Practices
-
-### 1. Use Descriptive Filenames
-
-```bash
-# Include context in filename
-playwright-cli video-start recordings/login-flow-2024-01-15.webm
-playwright-cli video-start recordings/checkout-test-run-42.webm
-```
-
-### 2. Record entire hero scripts.
-
-When recording a video for the user or as a proof of work, it is best to create a code snippet and execute it with run-code.
-It allows inserting appropriate pauses between the actions and annotating the video. There are new Playwright APIs for that.
-
-1) Perform scenario using CLI and take note of all locators and actions. You'll need those locators to request their bounding boxes for highlight.
-2) Create a file with the intended script for video (below). Use pressSequentially w/ delay for nice typing, make reasonable pauses.
-3) Use playwright-cli run-code --filename your-script.js
-
-**Important**: Overlays are `pointer-events: none` — they do not interfere with page interactions. You can safely keep sticky overlays visible while clicking, filling, or performing any actions on the page.
-
-```js
-async page => {
-  await page.screencast.start({ path: 'video.webm', size: { width: 1280, height: 800 }, fps: 60 });
-  // Show the cursor and mark the click point, and pace actions by 800ms.
-  await page.screencast.showActions({
-    duration: 800,
-    style: {
-      point: 'width: 20px; height: 20px; border-radius: 50%; background: rgba(255, 0, 0, .7)',
-      title: 'display: none',
-    },
-  });
-  await page.goto('https://demo.playwright.dev/todomvc');
-
-  // Show a chapter card — blurs the page and shows a dialog.
-  // Blocks until duration expires, then auto-removes.
-  // Use this for simple use cases, but always feel free to hand-craft your own beautiful
-  // overlay via await page.screencast.showOverlay().
-  await page.screencast.showChapter('Adding Todo Items', {
-    description: 'We will add several items to the todo list.',
-    duration: 2000,
-  });
-
-  // Perform action
-  await page.getByRole('textbox', { name: 'What needs to be done?' }).pressSequentially('Walk the dog', { delay: 60 });
-  await page.getByRole('textbox', { name: 'What needs to be done?' }).press('Enter');
-  await page.waitForTimeout(1000);
-
-  // Show next chapter
-  await page.screencast.showChapter('Verifying Results', {
-    description: 'Checking the item appeared in the list.',
-    duration: 2000,
-  });
-
-  // Add a sticky annotation that stays while you perform actions.
-  // Overlays are pointer-events: none, so they won't block clicks.
-  const annotation = await page.screencast.showOverlay(`
-    <div style="position: absolute; top: 8px; right: 8px;
-      padding: 6px 12px; background: rgba(0,0,0,0.7);
-      border-radius: 8px; font-size: 13px; color: white;">
-      ✓ Item added successfully
-    </div>
-  `);
-
-  // Perform more actions while the annotation is visible
-  await page.getByRole('textbox', { name: 'What needs to be done?' }).pressSequentially('Buy groceries', { delay: 60 });
-  await page.getByRole('textbox', { name: 'What needs to be done?' }).press('Enter');
-  await page.waitForTimeout(1500);
-
-  // Remove the annotation when done
-  await annotation.dispose();
-
-  // You can also highlight relevant locators and provide contextual annotations.
-  const bounds = await page.getByText('Walk the dog').boundingBox();
-  await page.screencast.showOverlay(`
-    <div style="position: absolute;
-      top: ${bounds.y}px;
-      left: ${bounds.x}px;
-      width: ${bounds.width}px;
-      height: ${bounds.height}px;
-      border: 1px solid red;">
-    </div>
-    <div style="position: absolute;
-      top: ${bounds.y + bounds.height + 5}px;
-      left: ${bounds.x + bounds.width / 2}px;
-      transform: translateX(-50%);
-      padding: 6px;
-      background: #808080;
-      border-radius: 10px;
-      font-size: 14px;
-      color: white;">Check it out, it is right above this text
-    </div>
-  `, { duration: 2000 });
-
-  await page.screencast.stop();
-}
-```
-
-Embrace creativity, overlays are powerful.
-
-### Overlay API Summary
-
-| Method | Use Case |
-|--------|----------|
-| `page.screencast.showChapter(title, { description?, duration?, styleSheet? })` | Full-screen chapter card with blurred backdrop — ideal for section transitions |
-| `page.screencast.showOverlay(html, { duration? })` | Custom HTML overlay — use for callouts, labels, highlights |
-| `disposable.dispose()` | Remove a sticky overlay added without duration |
-| `page.screencast.hideOverlays()` / `page.screencast.showOverlays()` | Temporarily hide/show all overlays |
-| `page.screencast.showActions({ cursor, duration, position, style })` | Cursor, click point, target highlight and action title |
-| `page.screencast.hideActions()` | Stop annotating actions and hide the cursor |
-
-### 3. Attach the recording to the pull request
-
-A hero script recording is the best proof of work for a user-facing change. GitHub accepts WebM as is, so once the recording looks right, attach it with `gh` 2.99+ instead of describing the flow in words:
-
-```bash
-gh pr create --title "feat(todo): add items inline" --body-file body.md --attach ./demo.webm
-gh pr comment 123 --body "Walkthrough of the new flow." --attach ./demo.webm
-gh issue comment 456 --body "Recording of the repro steps." --attach ./repro.webm
-```
-
-`gh` appends unreferenced attachments to the end of the body, which is the right place for a walkthrough. Videos are limited to 10 MB on free plans and 100 MB on paid plans, so keep the script focused, record at a modest size such as 1280x800 and drop chapters that do not add to the story. See [pr-attachments.md](pr-attachments.md) for the full set of commands, including attaching test artifacts from CI.
-
-## Tracing vs Video
-
-| Feature | Video | Tracing |
-|---------|-------|---------|
-| Output | WebM file | Trace file (viewable in Trace Viewer) |
-| Shows | Visual recording | DOM snapshots, network, console, actions |
-| Use case | Demos, documentation | Debugging, analysis |
-| Size | Larger | Smaller |
-
-## Limitations
-
-- Recording adds slight overhead to automation
-- Large recordings can consume significant disk space

package/skills/skills.lock.json

@@ -1,89 +0,0 @@
-{
-  "sources": [
-    {
-      "source": "testomatio/skills",
-      "ref": null,
-      "sha": "e1cf03227adfcb553c94ea5ee08c0eebc397e875",
-      "folder": "testomatio",
-      "skills": [
-        "automate-manual-test-cases",
-        "catalog-features",
-        "debug-fix-failed-flaky-autotests",
-        "detect-duplicate-test-cases",
-        "detect-product-mismatches",
-        "detect-useless-tests",
-        "epic-requirements-specification",
-        "explorbot-fundamentals",
-        "explorbot-plan",
-        "explorbot-setup",
-        "improve-test-cases",
-        "migrate-to-testomatio",
-        "prima",
-        "pull-request-diff-analyzer",
-        "qa-automation-test-consolidation",
-        "qa-data-seeder",
-        "qa-e2e-tests-reporting",
-        "qa-explain-behavior",
-        "qa-lead-strategy-advisor",
-        "qa-pr-requirements-analyzer",
-        "qa-requirement-reviewer",
-        "qa-review-pr",
-        "qa-split-testing-levels-pyramid",
-        "qa-sprint-report-by-testomatio",
-        "qa-test-code-coverage",
-        "qa-thinking",
-        "qa-write-test-cases",
-        "run-tests-with-testomatio-reporter",
-        "scan-automation-project",
-        "setup-change-aware-pr-testing",
-        "setup-ci-automation",
-        "sync-test-cases-with-tms",
-        "testing-workflow",
-        "testomat-allure-adapter",
-        "testomatio-mcp",
-        "wiki-from-code",
-        "write-user-story"
-      ]
-    },
-    {
-      "source": "codeceptjs/skills",
-      "ref": null,
-      "sha": "c9a82e3e237c908ba53ec47d2c841c680b88e03a",
-      "folder": "codeceptjs",
-      "skills": [
-        "ci-fix-tests",
-        "codeceptjs-auth",
-        "codeceptjs-exploration",
-        "codeceptjs-fundamentals",
-        "codeceptjs-run-analysis",
-        "debugging-codeceptjs-tests",
-        "lint-codeceptjs-tests",
-        "migrate-codeceptjs-4",
-        "migrate-cypress-to-codeceptjs",
-        "migrate-protractor-to-codeceptjs",
-        "migrate-selenium-java-to-codeceptjs",
-        "migrate-testcafe-to-codeceptjs",
-        "refactoring-codeceptjs-tests",
-        "writing-codeceptjs-tests"
-      ]
-    },
-    {
-      "source": "currents-dev/playwright-best-practices-skill",
-      "ref": null,
-      "sha": "283d5cbc5d11aac1abda058b16ad22c317d54dc0",
-      "folder": "playwright",
-      "skills": [
-        "playwright-best-practices"
-      ]
-    },
-    {
-      "source": "microsoft/playwright-cli/tree/main/skills/playwright-cli",
-      "ref": null,
-      "sha": "b1a5903c5b633b8c9f843ad7b629c2a78437040c",
-      "folder": "playwright",
-      "skills": [
-        "playwright-cli"
-      ]
-    }
-  ]
-}

package/skills/skills.yaml

@@ -1,35 +0,0 @@
-# External skills for Testeiya. ONE rule: every line is a GitHub repo.
-#
-#   owner/repo                        a skill repo (one skill, or many)
-#   owner/repo/tree/<ref>/<subdir>    pin a branch/tag/commit, or point at a subfolder
-#
-# Each source owns one vendor folder next to this file — the repo name, or the
-# owner when the repo is just "skills" (testomatio/skills -> testomatio/).
-# Updates replace only that folder; a folder this file does not own is treated
-# as internal and never touched. First-party skills are not kept here.
-#
-# Vendored folders are gitignored: they belong to their authors, under their own
-# licences. Send patches for them upstream, to the repo listed below.
-#
-# The folder is the category, and the repo decides it:
-#   - repo with a Claude-plugin marketplace (.claude-plugin/marketplace.json)
-#     -> one category subfolder per plugin  (testomatio/ -> test-management / test-automation / explorbot)
-#   - repo without one -> skills sit right under the vendor folder (the vendor is the category)
-#
-# Name the folder here when repos from different owners belong under one
-# category — the sources then share it, each skill in its own subfolder:
-#
-#   - source: owner/repo
-#     folder: playwright
-#
-# Edit the list, then run:  bunosh skills:update [vendor]      See the result:  bunosh skills:list
-
-- testomatio/skills
-- codeceptjs/skills
-
-# One Playwright category, two upstreams.
-- source: currents-dev/playwright-best-practices-skill
-  folder: playwright
-- source: microsoft/playwright-cli/tree/main/skills/playwright-cli
-  folder: playwright
-