Skip to content
Back to skills

Browser E2e Tester

ASecurity

Browser-based E2E testing for feature verification. Use when running end-to-end tests, validating features in browser, verifying user flows, or testing feature completion.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added February 8, 2026
testingpythongotestingapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add adaptationio/Skrillz --skill browser-e2e-tester --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Browser E2e Tester?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Browser E2e Tester
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/adaptationio-browser-e2e-tester/badge)](https://www.skillsdirectory.com/skills/adaptationio-browser-e2e-tester)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: browser-e2e-tester
description: Browser-based E2E testing for feature verification. Use when running end-to-end tests, validating features in browser, verifying user flows, or testing feature completion.
version: 1.0.0
category: autonomous-coding
layer: verification-recovery
---

# Browser E2E Tester

Runs browser-based end-to-end tests to verify feature implementation meets acceptance criteria.

## Quick Start

### Run Feature Tests
```python
from scripts.e2e_tester import E2ETester

tester = E2ETester(project_dir)
result = await tester.test_feature("auth-001")

if result.passed:
    print(f"Feature verified: {result.feature_id}")
else:
    print(f"Failed: {result.failures}")
```

### Run All Tests
```python
results = await tester.test_all_features()
print(f"Passed: {results.passed}/{results.total}")
```

## E2E Testing Workflow

```
┌─────────────────────────────────────────────────────────────┐
│                    E2E TEST WORKFLOW                        │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  1. SETUP                                                   │
│     ├─ Load feature acceptance criteria                    │
│     ├─ Start test server (if needed)                       │
│     ├─ Initialize browser automation                       │
│     └─ Set test timeout                                    │
│                                                             │
│  2. EXECUTE                                                 │
│     ├─ Navigate to feature entry point                     │
│     ├─ Execute test steps                                  │
│     ├─ Capture screenshots on failure                      │
│     └─ Record test artifacts                               │
│                                                             │
│  3. VERIFY                                                  │
│     ├─ Check expected outcomes                             │
│     ├─ Validate UI state                                   │
│     ├─ Verify API responses                                │
│     └─ Assert data persistence                             │
│                                                             │
│  4. REPORT                                                  │
│     ├─ Generate test report                                │
│     ├─ Update feature status                               │
│     └─ Store failure artifacts                             │
│                                                             │
└─────────────────────────────────────────────────────────────┘
```

## Test Result Structure

```python
@dataclass
class TestResult:
    feature_id: str
    passed: bool
    duration_ms: int
    steps_executed: int
    steps_passed: int
    failures: list[str]
    screenshots: list[Path]
    artifacts: dict
```

## Supported Test Frameworks

| Framework | Integration | Use Case |
|-----------|-------------|----------|
| **Playwright** | Native | Modern web apps |
| **Puppeteer** | Adapter | Chrome-focused |
| **Selenium** | Adapter | Legacy browsers |
| **Cypress** | CLI | Component tests |

## Feature Acceptance Format

```json
{
  "feature_id": "auth-001",
  "acceptance_criteria": [
    {
      "step": "Navigate to login page",
      "action": "goto",
      "target": "/login"
    },
    {
      "step": "Enter credentials",
      "action": "fill",
      "target": "#email",
      "value": "test@example.com"
    },
    {
      "step": "Submit form",
      "action": "click",
      "target": "button[type=submit]"
    },
    {
      "step": "Verify redirect",
      "action": "assert_url",
      "expected": "/dashboard"
    }
  ]
}
```

## Integration Points

- **coding-agent**: Triggers tests after implementation
- **progress-tracker**: Reports test metrics
- **error-recoverer**: Handles test failures
- **checkpoint-manager**: Restores state on failure

## References

- `references/E2E-PATTERNS.md` - Test patterns
- `references/BROWSER-AUTOMATION.md` - Automation guide

## Scripts

- `scripts/e2e_tester.py` - Core tester
- `scripts/browser_controller.py` - Browser automation
- `scripts/test_reporter.py` - Report generation
- `scripts/acceptance_parser.py` - Criteria parser

Files in this skill

  • SKILL.md4.7 KB
  • references/E2E-PATTERNS.md4.9 KB
  • scripts/acceptance_parser.py5.2 KB
  • scripts/browser_controller.py6.9 KB
  • scripts/e2e_tester.py6.1 KB
  • scripts/test_reporter.py5.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.