testing

Testing – Contentstack Management JavaScript SDK

When to use

• Running npm run test:unit, sanity, or Jest.
• Adding or changing tests under test/unit/ or test/sanity-check/.
• Configuring env vars for live CMA sanity runs.

Instructions

Commands (from package.json)

Always npm run build before sanity if dist/node/contentstack-management.js must match lib/ (sanity imports the built artifact).

Unit tests (test/unit/)

• Mocha + Chai + @babel/register; 30s timeout per script.
• HTTP: mock with Nock, axios-mock-adapter, or stubs — no live CMA.
• Suites are required from test/unit/index.js — add new *-test.js files and register them there.

Sanity tests (test/sanity-check/)

• Live CMA calls; orchestrated by test/sanity-check/sanity.js.
• Authoritative env list: test/sanity-check/utility/testSetup.js (and sanity.js).

Environment variables

Required (core) — setup fails without: EMAIL, PASSWORD, HOST, ORGANIZATION.

Suite-specific (tests skip or degrade when missing):

Optional: PERSONALIZE_HOST, DELETE_DYNAMIC_RESOURCES (defaults in setup). Set HOST to your CMA API host.

Runtime: setup assigns API_KEY, AUTHTOKEN, MANAGEMENT_TOKEN, etc. — do not commit those.

Jest (test/typescript/)

• jest.config.js: ts-jest, coverage under coverage/.

Hygiene

• No committed only / skip for CI-needed tests.
• Never commit real tokens in tests or snapshots.