Skip to content
Skills Library
Programming · Testing

grb-testing

/grb-testing

Use when adding or running tests for the Go React boilerplate. Covers Go unit tests, Vitest, Playwright, the demo accounts, rate limits, cleanup rules and the Docker test stack.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 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
1
Deprecation

No signals detected. Repository changed on 13.11.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

Use when adding or running tests for the Go React boilerplate. Covers Go unit tests, Vitest, Playwright, the demo accounts, rate limits, cleanup rules and the Docker test stack.

Original author description

Use when adding or running tests for the Go React boilerplate. Covers Go unit tests, Vitest, Playwright, the demo accounts, rate limits, cleanup rules and the Docker test stack.

How it works

  1. Go unit tests
  2. Vitest
  3. Playwright
  4. Run
  5. Before you finish
Original SKILL.md headings · 57 lines, 253 words
SKILL.md preview
---
name: grb-testing
description: Use when adding or running tests for the Go React boilerplate. Covers Go unit tests, Vitest, Playwright, the demo accounts, rate limits, cleanup rules and the Docker test stack.
---

# Testing

Three layers, one command each.

## Go unit tests

- Same package as the code.
- Cover policies, validation, config and security primitives.
- Use table-driven tests.
- Do not mock gorm or HTTP internals. Put fakes at port boundaries.
- Run `go test ./cmd/... ./internal/...`.

## Vitest

- `web/src/**/*.test.{ts,tsx}`.
- Use Testing Library with `jsdom`.
- Cover i18n, helpers and pure UI logic.
- Run `cd web && npm test`.

## Playwright

- Specs: `web/tests/e2e/*.spec.ts`.
- Default base URL: `http://127.0.0.1:3000`.
- Override with `E2E_BASE_URL`.
- Demo accounts use password `password`.
- Set the `locale=en` cookie in `beforeEach` for English assertions.
- Use unique emails and role names with a timestamp.
- Clean up users, roles and settings in `finally`.
- Re-login as the superadmin before admin cleanup after an API test signs in
  as a lower-privileged account.
- The auth rate limit is 20 requests per minute per IP by default. Keep the
  suite under it or raise `RATE_LIMIT_PER_MINUTE` for a test run.

## Run

```bash
make test              # Go + Vitest
make test-e2e-install  # once
make test-e2e          # against a running app
```

For a full local check:

```bash
docker compose up --build -d
make test-e2e
```

## Before you finish

- [ ] `make lint` passes.
- [ ] `make test` passes.
- [ ] The affected Playwright spec passes.
- [ ] The seed is back to 14 users, 3 roles, approval off and 2FA off.
- [ ] No test artifacts remain in `web/test-results` or `web/playwright-report`.

Versions

The database has no other skills named grb-testing.

Database snapshot: 13.11.2026 · package version 5c30d81a51ae (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

  • 100nextjs-testing
    Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.
  • 90Vitest
    Expert guidance for Vitest testing framework including unit tests, integration tests, mocking, coverage, React Testing Library integration, and TypeScript testing. Use this when writing tests for Vite-based applications.
  • 100react-vitest
    Use when adding or improving tests in a React project that uses Vitest — covers component testing with Testing Library, mocking hooks, and coverage configuration.
  • 100vitest-testing-patterns
    Write tests using Vitest and React Testing Library. Use when creating unit tests, component tests, integration tests, or mocking dependencies. Activates for test file creation, mock patterns, coverage, and testing best practices.
  • 100vitest-testing-patterns
    Write tests using Vitest and React Testing Library. Use when creating unit tests, component tests, integration tests, or mocking dependencies. Activates for test file creation, mock patterns, coverage, and testing best practices.
  • 100react-testing
    React component testing with Testing Library and Vitest. Covers unit tests, integration tests, async testing, mocking, user events, accessibility testing, and test patterns. USE WHEN: user mentions "React testing", "Testing Library", "Vitest", "component tests", "userEvent",…

Feedback and reports

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