contentstack/datasync-asset-store-filesystem · Archived

testing

Jest tests and coverage for datasync-asset-store-filesystem — use for test layout, pretest build, and coverage output.

First seen Jul 16, 2026

Installation

$ npx skills add contentstack/datasync-asset-store-filesystem --skill testing

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from contentstack/datasync-asset-store-filesystem.

npx skills add contentstack/datasync-asset-store-filesystem

Browse all from contentstack/datasync-asset-store-filesystem

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,202 B
  • docs SUMMARY.md 135 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Testing – DataSync Asset Store Filesystem

When to use

  • Adding or changing tests under test/
  • Interpreting coverage reports or Jest configuration
  • Debugging pretest / build ordering before tests run

Instructions

  • Runner: npm test runs Jest with --coverage. pretest runs npm run build-ts and removes _contents and coverage so tests run against a fresh build and clean asset dirs where relevant.
  • Test files: jest.config.js sets testRegex: "./test/..js$" and testEnvironment: "node". Tests are JavaScript under test/, not co-located .spec.ts in src/.
  • Coverage: Output directory coverage/; reporters include json and html. coveragePathIgnorePatterns excludes nodemodules, test-utils, testcontent, and parts of dist/ — adjust in jest.config.js if you add new paths that should be ignored or included.
  • Integration style: example/ and test/ may use mocks; avoid committing real API keys or secrets (align with Talisman/Snyk expectations if hooks are used).