contentstack/contentstack-dart · Archived

testing

Use for test layout, running tests, coverage, fixtures, and credential handling in this repo.

First seen Jul 16, 2026

Installation

$ npx skills add contentstack/contentstack-dart --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/contentstack-dart.

npx skills add contentstack/contentstack-dart

Browse all from contentstack/contentstack-dart

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 3
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,510 B
  • docs SUMMARY.md 108 B

History

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

SKILL.md

Testing – Contentstack Dart SDK

When to use

  • Adding or changing tests under test/
  • Running the suite locally or generating coverage
  • Dealing with API keys and environment variables for integration-style tests

Instructions

Layout and runner

  • Tests live in test/ (e.g. stacktest.dart, querytest.dart, entry_test.dart)
  • Run all: dart test
  • Optional coverage workflow and LCOV steps are documented in [test/runtest.sh](../../test/runtest.sh) (dart test --coverage=./coverage, coverage:format_coverage, etc.)

Credentials policy

  • Tests such as [test/stacktest.dart](../../test/stacktest.dart) load credentials via dotenv (apiKey, deliveryToken, environment, optional host)
  • Do not commit secrets—use local .env or CI secrets only as your team documents; never paste real tokens into the repo or PR descriptions

Scope

  • Prefer unit tests for pure logic; use guarded integration tests only when stack credentials are available
  • After codegen changes, ensure tests still pass and coverage excludes generated files if you use the scripts in test/run_test.sh

References

  • [../dev-workflow/SKILL.md](../dev-workflow/SKILL.md) — dart test in CI workflow
  • [../contentstack-dart-sdk/SKILL.md](../contentstack-dart-sdk/SKILL.md) — behavior under test
  • package:test