Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Testing Advanced

ASecurity

Advanced testing: E2E with Playwright/Cypress, property-based testing, mutation testing, contract testing, and CI/CD pipelines. Use when: (1) E2E tests with Playwright/Cypress, (2) Property-based testing with fast-check, (3) Mutation testing, (4) Contract testing with Pact, (5) CI/CD test pipelines, (6) Flaky test management. Auto-detects: playwright.config.*, cypress.config.*, e2e/, pact, fast-check, stryker, mutation in package.json

24 stars
0 votes
0 copies
0 views
Added 2/7/2026
developmenttypescriptgobashnodetestinggitapifrontenddevopsci/cd

Works with

cliapi

Security Analysis

A100/100

Scanned 2/12/2026

$npx -y skills add Fujigo-Software/f5-framework-claude --skill testing-advanced --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Testing Advanced?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Testing Advanced
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fujigo-software-testing-advanced/badge)](https://www.skillsdirectory.com/skills/fujigo-software-testing-advanced)

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

Download with Pro
Files
SKILL.md
---
name: testing-advanced
version: "1.0.0"
description: |
  Advanced testing: E2E with Playwright/Cypress, property-based testing,
  mutation testing, contract testing, and CI/CD pipelines.

  Use when: (1) E2E tests with Playwright/Cypress, (2) Property-based testing
  with fast-check, (3) Mutation testing, (4) Contract testing with Pact,
  (5) CI/CD test pipelines, (6) Flaky test management.

  Auto-detects: playwright.config.*, cypress.config.*, e2e/, pact, fast-check,
  stryker, mutation in package.json
related:
  - testing
  - devops
  - api-design
---

# Testing Advanced Skill

E2E, property-based, mutation, and CI/CD testing patterns.

## E2E with Playwright

```bash
npx playwright test           # Run all
npx playwright test --ui      # UI mode
npx playwright test --debug   # Debug mode
npx playwright codegen        # Generate tests
```

### Page Object Model

```typescript
// pages/LoginPage.ts
export class LoginPage {
  constructor(private page: Page) {}

  async login(email: string, password: string) {
    await this.page.fill('[data-testid="email"]', email);
    await this.page.fill('[data-testid="password"]', password);
    await this.page.click('[data-testid="submit"]');
  }

  async expectLoggedIn() {
    await expect(this.page).toHaveURL('/dashboard');
  }
}

// tests/auth.spec.ts
test('should login successfully', async ({ page }) => {
  const loginPage = new LoginPage(page);
  await page.goto('/login');
  await loginPage.login('user@test.com', 'password');
  await loginPage.expectLoggedIn();
});
```

### Visual Regression

```typescript
test('should match screenshot', async ({ page }) => {
  await page.goto('/dashboard');
  await expect(page).toHaveScreenshot('dashboard.png', {
    maxDiffPixels: 100,
  });
});
```

## Cypress Configuration

```typescript
// cypress.config.ts
export default defineConfig({
  e2e: {
    baseUrl: 'http://localhost:3000',
    supportFile: 'cypress/support/e2e.ts',
    specPattern: 'cypress/e2e/**/*.cy.ts',
  },
  retries: { runMode: 2, openMode: 0 },
});
```

## Property-Based Testing

```typescript
import fc from 'fast-check';

describe('string operations', () => {
  it('reverse(reverse(s)) === s', () => {
    fc.assert(
      fc.property(fc.string(), (s) => {
        return reverse(reverse(s)) === s;
      })
    );
  });

  it('sort is idempotent', () => {
    fc.assert(
      fc.property(fc.array(fc.integer()), (arr) => {
        const sorted = sort(arr);
        return JSON.stringify(sort(sorted)) === JSON.stringify(sorted);
      })
    );
  });
});
```

## Mutation Testing (Stryker)

```json
// stryker.conf.json
{
  "mutate": ["src/**/*.ts", "!src/**/*.spec.ts"],
  "testRunner": "jest",
  "reporters": ["html", "clear-text"],
  "thresholds": { "high": 80, "low": 60, "break": 50 }
}
```

```bash
npx stryker run
```

## Contract Testing (Pact)

```typescript
// Consumer test
const provider = new Pact({
  consumer: 'FrontendApp',
  provider: 'UserService',
});

describe('User API', () => {
  beforeAll(() => provider.setup());
  afterAll(() => provider.finalize());

  it('should get user', async () => {
    await provider.addInteraction({
      state: 'user exists',
      uponReceiving: 'get user request',
      withRequest: { method: 'GET', path: '/users/1' },
      willRespondWith: {
        status: 200,
        body: { id: 1, name: 'John' },
      },
    });

    const user = await getUser(1);
    expect(user.name).toBe('John');
  });
});
```

## CI/CD Pipeline (GitHub Actions)

```yaml
# .github/workflows/test.yml
name: Tests
on: [push, pull_request]

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: '20' }

      - run: npm ci
      - run: npm run test:cov

      - name: Upload coverage
        uses: codecov/codecov-action@v3
        with:
          files: ./coverage/lcov.info

  e2e:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4

      - run: npm ci
      - run: npx playwright install --with-deps
      - run: npm run test:e2e

      - uses: actions/upload-artifact@v4
        if: failure()
        with:
          name: playwright-report
          path: playwright-report/
```

## Flaky Test Management

```typescript
// Retry configuration
test.describe.configure({ retries: 2 });

// Wait for stability
await expect(element).toBeVisible({ timeout: 10000 });

// Avoid timing issues
await page.waitForLoadState('networkidle');
```

## F5 Quality Gates

| Gate | Requirement |
|------|-------------|
| G3 | E2E critical paths verified |
| G4 | Contract tests pass |
| G5 | Production smoke tests |

Attribution

Fujigo-SoftwareFujigo-Software
View sourceSee grades on GitHubMore from Fujigo-Software →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Clean Code

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

304955 votes

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

286712 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2222 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

2927051 votes
View all in development →