test

Automate end-to-end feature testing in the Carbon dev server.

2.3k|331|Updated Jun 3, 2024

Search Tags:#test automation #browser testing #end-to-end testing #feature testing #Carbon

Ready to run

npx skills add https://github.com/crbnos/carbon --skill test-crbnos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test
Source: https://github.com/crbnos/carbon/tree/main/.ai/skills/test
Command: npx skills add https://github.com/crbnos/carbon --skill test-crbnos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates end-to-end feature testing in the Carbon dev server, ensuring that changes and fixes work as intended in the browser environment.

Core Features & Use Cases

Feature Testing: Execute a test plan for a specific feature or GitHub issue.
Browser Testing: Simulate user interactions and verify results in the browser.
Playbook Caching: Cache successful test scenarios for reuse.
Use Case: After a pull request is merged, use this Skill to verify that the feature works correctly in the browser.

Quick Start

Run the test skill to verify the 'create a purchase order' feature in the Carbon dev server.

Frequently Asked Questions about test

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

FAQPage Schema

How do I automate end-to-end feature testing in a dev server?▼

Automate end-to-end feature testing by generating a test plan, simulating browser interactions, and verifying results directly in the dev server environment. This ensures code changes function as intended without manual checks.

Can I verify a GitHub issue fix using real browser execution?▼

Yes, you can verify a GitHub issue fix using real browser execution. The tool simulates user interactions based on the issue's branch diff to confirm the specific feature works correctly.

Do I need an active dev server to run browser testing for features?▼

Yes, an active dev server is required to run browser testing. The automation executes test plans directly against the live server environment to validate feature changes accurately.

How does playbook caching work for feature testing scenarios?▼

Playbook caching saves successful test scenarios for future reuse. When a feature test passes, the automation stores the playbook to quickly repeat the same browser interactions later.

What is the best way to verify a merged pull request in the browser?▼

The best way to verify a merged pull request is running an automated browser test against the feature. This executes a predefined test plan to validate user interactions and confirm the changes work.

How do I test a specific feature like creating a purchase order automatically?▼

To automatically test creating a purchase order, run the test skill targeting that feature. It generates a test plan, executes the browser interactions, and verifies the transaction completes successfully.