Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
contentstack avatar

Testing

  • 2 installs
  • 1 repo stars
  • Updated August 4, 2026
  • contentstack/contentstack-management-python

Test Contentstack CMS integrations and API operations in Python workflows.

About

Testing guidance for the Contentstack Management Python SDK covering content and asset operations. Validates authentication flows and CRUD operations against CMS endpoints.

  • Test authentication methods including tokens and user credentials
  • Validate CRUD operations on content types and entries

Testing by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #1,693 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/contentstack/contentstack-management-python --skill testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs2
repo stars1
Last updatedAugust 4, 2026
Repositorycontentstack/contentstack-management-python

What it does

Test Contentstack CMS integrations and API operations in Python workflows.

Files

SKILL.mdMarkdownGitHub ↗

Testing – Contentstack Management Python

When to use

  • Adding or changing tests under `tests/`.
  • Debugging API vs mock failures; improving `tests/cred.py` usage.

Instructions

Runner and tooling

SuitePathNotes
Unittests/unit/**Fast, isolated; primary CI target
APItests/api/**Live CMA — `.env` via `tests/cred.py`
Mocktests/mock/**Mocked HTTP / contracts
GoalCommand
Unit (CI-style)pytest tests/unit/ -v or coverage run -m pytest tests/unit/
API (live CMA)pytest tests/api/ -v
Mockpytest tests/mock/ -v
Full treepytest tests/ -v

Environment (tests/cred.py)

  • `get_credentials()` loads dotenv and returns host, tokens, and resource UIDs.
  • Common vars: `HOST`, `APIKEY`, `AUTHTOKEN`, `MANAGEMENT_TOKEN`, `ORG_UID`, plus resource UIDs as tests require.
  • Use a `.env` at repo root for local API runs; never commit secrets.

Hygiene

  • No committed secrets; use placeholders or env-only values for CI.
  • Avoid leaving `pytest.skip` or focused-only tests enabled in paths meant for full suite runs unless intentional.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.