steedos-dev-testing

Automates iterative build, restart, and browser testing of Steedos projects using Playwright MCP.

1.6k|414|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/steedos/steedos-platform --skill steedos-dev-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steedos-dev-testing
Source: https://github.com/steedos/steedos-platform/tree/main/skills/steedos-dev-testing
Command: npx skills add https://github.com/steedos/steedos-platform --skill steedos-dev-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually rebuilding, restarting, and verifying Steedos project changes in a browser is slow and error-prone. This Skill standardizes an AI-driven dev-test loop so code changes are built, deployed, and verified automatically until they pass.

Core Features & Use Cases

  • Dev-Test Loop Automation: Runs an 8-step cycle (analyze, modify, build, restart, wait, test, record, iterate) for every change request.
  • Playwright MCP Browser Testing: Mandates browser automation for login, page verification, CRUD operations, and export/download checks.
  • Project Configuration Template: Generates a .github/copilot-instructions.md file capturing test URL, credentials, build/start commands, and port settings.
  • Use Case: Tell the AI "fix the Excel export feature and test until it passes" — it will modify code, rebuild, restart the server on port 5100, log in via Playwright MCP, and iterate until verification succeeds.

Quick Start

Ask the AI to set up the automated dev test environment for your Steedos project, then describe the bug or feature you want fixed and tested.

Frequently Asked Questions about steedos-dev-testing

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

FAQPage Schema
How do I automate testing of a Steedos project with Playwright?

Configure a copilot-instructions.md file with your test URL, credentials, and build commands, then describe your task to the AI. It runs a dev-test loop using Playwright MCP Server for browser automation, covering login, navigation, and CRUD verification.

How to set up a dev test environment for Steedos development?

Tell the AI to configure the dev test environment and provide your test URL, login credentials, working directory, build and start commands, and port. The AI generates a .github/copilot-instructions.md file that drives all subsequent test iterations.

Is Playwright MCP required for Steedos project testing?

Yes, this workflow mandates Playwright MCP Server for all browser automation testing in Steedos projects. It handles login, page snapshots, form filling, clicks, and failure screenshots as the standard verification method.

What should I do when the Steedos server port is already occupied?

Kill the process occupying the port with lsof -ti:{PORT} | xargs kill -9, then rebuild and restart the server. The skill's troubleshooting table also covers build failures, page loading issues, and login errors.

When should I not use this dev-testing workflow?

Use other skills for metadata changes that don't need browser testing: steedos-objects for object and field definitions, steedos-pages for UI pages, and steedos-server-logic for backend logic. This skill focuses on the build-test iteration loop.