Postman & Testing

Postman requirements

The main collection must reserve a dedicated folder named Legacy Despacho.

That folder exists to make the scope visible even before every request is fully materialized.

Recommended variables:

• legacyBasePath
• legacyGuid
• legacyUsuario
• legacyPassword

Coverage rule

Each migrated legacy service should end with:

1. a public docs page in this section
2. a Postman request or documented placeholder in the Legacy Despacho folder
3. at least one regression fixture for request and response compatibility

Current status

• the GeoTareas Postman collection was originally created for apidev/v1
• Legacy Despacho needed a dedicated scope and dedicated variables
• request examples for not-yet-implemented adapters should not be invented

Testing policy

Legacy compatibility is not complete without contract regression checks.

Recommended verification per endpoint:

• legacy request fixture
• legacy response fixture
• auth validation fixture
• negative case fixture when the original contract exposes a functional error message