Index of every page on this site: llms.txt
All skills
Run it yourself

Sounding-first testing patterns for The Boring JavaScript Stack — one test() API, a Sails-centered trial context, worlds under tests/, JSON and Inertia request testing, mail capture, and browser-capable trials only when the browser truly matters. Use this skill when writing, configuring, or debugging tests in a Sails.js + Inertia.js application.

Use this Skill: https://skilld.dev/gh/sailscastshq/boring-stack/testing

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈692 when used: this file. ≈5.1k more on demand in 7 files.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈357 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Testing

The Boring JavaScript Stack now has one primary testing story: Sounding.

Sounding keeps the familiar test() API, but gives Sails apps one coherent runtime for:

  • helper and business-logic trials
  • JSON endpoint and policy behavior
  • Inertia page contracts
  • mail assertions
  • browser-capable flows when the browser truly matters

When to Use

Use this skill when:

  • Writing or restructuring tests in a Sails.js + Inertia.js application
  • Migrating older node:test, Playwright, or inertia-sails/test suites to Sounding
  • Designing tests/unit, tests/e2e/pages, tests/factories, and tests/scenarios
  • Configuring config/sounding.js and config/env/test.js
  • Writing trials around sails.helpers, get() / post(), visit(), auth, login, mailbox, or page
  • Choosing between virtual transport and real HTTP transport
  • Keeping mail capture, datastore isolation, and browser setup calm and predictable
  • Selecting named browser projects such as desktop, mobile, or safari
  • Debugging failed browser trials with Sounding's default URL/screenshot artifacts and opt-in traces/videos
  • Setting up CI around a Sounding-powered suite

Sounding Mental Model

Keep these terms straight and use them consistently:

  • a trial is one named behavior the app must prove
  • the trial context is the object Sounding passes into test()
  • sails is the canonical center of that context
  • a world is the named business situation the trial lives inside
  • an actor is the role operating through that world
  • a suite is the whole organized test tree for the app

Prefer Sounding's public shape:

  • const { test } = require('sounding')
  • test('...', async ({ sails, get, visit, auth, login, page, expect }) => {})
  • sails.helpers.*
  • sails.sounding.*

Do not push people back toward:

  • ad hoc getSails() boot helpers
  • inertia-sails/test as the main integration story
  • Playwright for every request-level behavior
  • tests/sounding/ as a framework-branded island

Rules

Read the rule files that match the work you are doing:

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides comprehensive testing guidelines and best practices for developers using The Boring JavaScript Stack and the Sounding framework. It covers unit, integration, and end-to-end testing without introducing any security risks or malicious behaviors.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    8/8 files flagged

Signed by skilld at ce3d93c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 5 months ago
Other metadata
metadata
{
  "author": "sailscastshq",
  "version": "2.0.0",
  "tags": "testing, sounding, sails, node-test, playwright, inertia, e2e, unit-tests, boring-stack"
}

README badge

README badge for sailscastshq/boring-stack/testing