Skip to content
Skills Library
Programming · Testing

test-e2e

/test-e2e

End-to-end user workflow testing. Test complete user flows from action to result. Use when testing full stack, customer scenarios, or complete purchase/login/flow paths.

Repository
vant ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

End-to-end user workflow testing. Test complete user flows from action to result. Use when testing full stack, customer scenarios, or complete purchase/login/flow paths.

Original author description

End-to-end user workflow testing. Test complete user flows from action to result. Use when testing full stack, customer scenarios, or complete purchase/login/flow paths.

How it works

  1. When To Use
  2. What To Test
  3. Tools
  4. Output
Original SKILL.md headings · 70 lines, 190 words
SKILL.md preview
---
name: test-e2e
description: End-to-end user workflow testing. Test complete user flows from action to result. Use when testing full stack, customer scenarios, or complete purchase/login/flow paths.
license: MIT
metadata:
  author: vant
  version: "1.0"
---

# Test E2E

> End-to-end user workflows.

## When To Use

- Complete user flows
- Full stack testing
- Customer scenarios

## What To Test

### 1. User Flow

```
User action → API → Database → UI update
```

Example: Login → Cart → Checkout → Confirmation

### 2. Critical Paths

| Path | User Action | Expected |
|------|------------|----------|
| Signup | Account created | Yes |
| Login | Authenticated | Yes |
| Purchase | Order confirmed | Yes |
| Search | Results shown | Yes |

### 3. Test Example

```javascript
test('complete purchase flow', async () => {
  await login.valid()
  await cart.add(item)
  await checkout.pay()
  await confirmation.seen()
})
```

---

## Tools

| Tool | Use |
|------|-----|
| Playwright | Browser automation |
| Cypress | E2E testing |
| Puppeteer | Headless Chrome |
| Selenium | Cross-browser |

---

## Output

```
## E2E Tests

| Flow | Status |
|------|--------|
| Signup | [PASS/FAIL] |
| Login | [PASS/FAIL] |
| Purchase | [PASS/FAIL] |
| Search | [PASS/FAIL] |
```

**Role**: E2E Tester  
**Input**: User flow  
**Output**: Test results

Versions

The database has no other skills named test-e2e.

Database snapshot: 13.11.2026 · package version d0b0da8bf9bd (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100running-e2e-tests
    Execute end-to-end tests covering full user workflows across frontend and backend. Use when performing specialized testing. Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".
  • 100e2e-playwright-testing
    End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/.
  • 100argent-test-ui-flow
    Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running UI test scenarios, manual QA steps, visible UI changes, or visual behavior.
  • 100running-e2e-tests
    Execute end-to-end tests covering full user workflows across frontend and backend. Use when performing specialized testing. Trigger with phrases like "run end-to-end tests", "test user flows", or "execute E2E suite".
  • 100auracheck-tester
    Use when the user wants a website or web app tested, QA'd, or checked for bugs — "test this site", "find bugs on <url>", "write a test suite / test cases for <url>", release QA, regression or smoke tests before a deploy, end-to-end (E2E) testing of a login, checkout, form, or…
  • 100test-plan
    Plan and check testing for a feature: map each acceptance criterion to a test at the right level, find gaps, write the missing tests, and run end-to-end checks of the main flows. Use when a feature needs a test strategy or before review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.