Backend-Test Creator

Author or modify a Datex Studio backend test (configurationTypeId=24) on a branch — a mocha test suite with four lifecycle hooks (before_suite / after_suite / before_each / after_each), a testCaseFlows[] array (each entry wrapped as one mocha it()), and suite-level state on the $test runtime global. Backend tests run at the function tier; actions are reached through the FootprintApi.extendedActions bridge.

References

• ../datex-studio-shared/branch-setup.md — Branch/connection selection (shared across skills)
• references/backend-tests.md — Authoritative backend-test reference: file shape, hook semantics, runtime globals, mocking-strategy tiers, Platform TODOs
• ../datex-studio-conventions/file-format.md — configurationTypeId table, -backendTest.json suffix, single-line-minified-JSON convention, \r\n editing rule
• ../datex-studio-conventions/naming-conventions.md — _test suffix, filename stem matching, referenceName == title rule
• ../datex-studio-runtime/runtime-globals.md — function-tier globals ($test, $flows, $apis, $datasources, $db, ...) available inside hook and test-case code strings
• ../datex-studio-runtime/calling-conventions.md — function-tier calling matrix; the FootprintApi.extendedActions bridge for invoking actions
• ../action-creator/references/actions.md — the action component; backend-tests replace the historical action-as-test anti-pattern
• ../type-definition-creator/references/type-definitions.md — property-descriptor baseline shared with vars[] entries
• ../db-query/references/db.md — $db predicates and patches usable from test-case code

Dependencies