Repository navigation
EN Testing and CI
English · Türkçe · Languages / Diller
Scope: JSON API Forge 0.5.1 · Source review: 17 September 2026 · Language: English
Each product branch owns its source and workflows. A passing result for one component does not verify all others. Distinguish workflow definitions from actual completed CI runs.
python -m pip install -e ".[dev]"
forge validate
forge doctor
pytest -q
python -m build
python -m twine check dist/*Keep live .env values and databases out of test environments. Real PostgreSQL/Redis/Mongo integration tests need the services defined by the workflow. Unit-test success does not establish real-driver integration.
| Component | Coverage areas |
|---|---|
main |
Python 3.10–3.14, coverage, SQL/Redis/Mongo, packaging, TypeScript, Docker, CodeQL, manifest |
python-library |
Cross-platform Python, package/typing metadata, reproducibility, contract tests against main
|
Editor |
Six native targets, warnings-as-errors, Qt tests, packaged screenshots, ZIP and IFW installers |
exampleApps |
Schema/CRUD/RPC/realtime/graph smoke checks for 25 apps using a separate runtime checkout |
SDK/Editor/examples workflows build artifacts. That does not itself publish to PyPI or GitHub Releases; official release publication is a separate operator step. MANIFEST.sha256 describes tracked source integrity, while an archive's .sha256 sidecar is a different file.
- Can a second tenant access the same resource ID?
- Does one idempotency key avoid duplicate side effects?
- Does invalid JSON reload preserve the last valid application?
- Does an expired Editor session lose access while unsaved text is retained?
- Does saving with an old document SHA return 409?
- Is a cursor resource accidentally connected to an offset iterator?
- Are packaged Qt dependencies available on a clean machine?
Source commits are pinned in versions and compatibility. Field and API references are generated from schemas/AST. Initial commands and CRUD/RPC/hook examples run in disposable test directories. VERIFICATION.md in the package records actual checks and platform limitations.
Documentation verification does not rerun the entire official CI matrix. For later versions, rerun tests relevant to changed behavior; an older verification report is not certification of a newer release.
This page describes the behavior at the pinned commits below. Recheck these contracts when upgrading.
main/.github/workflows/ci.ymlpython-library/.github/workflows/python-library.ymlEditor/.github/workflows/editor-build.ymlexampleApps/.github/workflows/example-apps.yml