skills.rest
VBaranouski
VBaranouskiCOMMUNITY
Explore all skills by this author →
GitHub

create-auto-tests

Convert tracker DB entries into Playwright test specs and update results.

Updated Aug 23, 2026
Search Tags:#e2e#playwright#test-automation#tracker#picasso
One-click install
npx skills add https://github.com/VBaranouski/PIC_Automation --skill create-auto-tests
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-auto-tests
Source: https://github.com/VBaranouski/PIC_Automation/tree/main/.agents/skills/create-auto-tests
Command: npx skills add https://github.com/VBaranouski/PIC_Automation --skill create-auto-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate tracker DB scenarios into automated Playwright tests for PICASso features and synchronize results back to the tracker as tests evolve.

Core Features & Use Cases

  • Create new test specs from pending tracker scenarios across any feature area.
  • Fix failures by updating locators after OutSystems UI changes and stabilizing flaky tests.
  • Extend existing specs and batch-automate scenarios across workflows; keep tracker status in sync.
  • Run headed or headless validations to ensure end-to-end coverage before release.

Quick Start

Invoke /create-auto-tests with the desired scenario IDs, feature area, or next pending batch to start automating tests.

Frequently Asked Questions about create-auto-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert tracker scenarios into Playwright test specs?▼

Update Playwright locators after OutSystems UI changes by using the /create-auto-tests command to fix failing tests, stabilize flaky scenarios, and validate updates via headed or headless browser executions before release.

Can I batch-automate end-to-end test scenarios across different workflows?▼

Yes, you can batch-automate end-to-end test scenarios across workflows by invoking /create-auto-tests with the next pending batch, which processes multiple tracker DB entries and keeps the tracker status synchronized as tests evolve.

How do I run headed or headless validations for automated test specs?▼

Run headed or headless validations for automated test specs by triggering the /create-auto-tests workflow, which coordinates execution modes to ensure end-to-end coverage for PICASso features before deployment.

Why does my Playwright test fail after an OutSystems UI update?▼

Playwright tests fail after OutSystems UI updates because element locators change, requiring you to use the test automation workflow to update locators, stabilize flaky tests, and validate fixes before syncing results back to the tracker.

What is the best way to keep tracker DB status synchronized with automated test results?▼

The best way to keep tracker DB status synchronized with automated test results is to use /create-auto-tests, which automatically updates the tracker database as Playwright test specs are created, fixed, extended, or batch-validated.

Related Skills

Explore More Software Engineering Skills→
nebuladevopsnebuladevops

e2e-next-test

Parse COVERAGE_PLAN.md to identify the next pending E2E test case.

Community
Advanced
DubDev720DubDev720
2

release-pipeline-validation-workflow

Orchestrate a deterministic CI/CD release pipeline for Godot projects with staged smoke verification.

Community
Advanced
ProfPowellProfPowell
4

e2e-testing

Run end-to-end browser tests with Playwright for user flows and visual regression.

Community
Advanced
dennisonbertramdennisonbertram
1

cypress-testing

Automate end-to-end and component tests with Cypress for web UI verification.

Community
Intermediate