gate-4a-unit-tests

To enforce nock-only HTTP mocking in TypeScript unit tests, validate test suites against project standards that reject forbidden libraries and require nock for network interception. This prevents real network calls during unit test execution.

A valid TypeScript unit test structure requires test files within a test/unit directory, properly formatted describe/it blocks, a minimum number of test cases, and Common.ts helpers to maintain consistency across the service testing workflow.

Unit tests fail gating requirements when they lack sufficient describe blocks, miss afterEach cleanup routines, use forbidden libraries, or improperly rely on environment variables instead of mocking HTTP calls with nock.

Ensure test isolation with nock by implementing afterEach cleanup blocks in your TypeScript test suites. This clears mock interceptors after each test case, preventing mock state from leaking across unit tests.

No, you cannot use environment variables in unit tests for TypeScript services. Enforcing strict gating requirements prohibits environment variables to ensure tests remain isolated, deterministic, and fully mocked using nock.