What this easeia rename test verifies
easeia rename test confirms the Easeia rename and dead-code cleanup did not break the publish pipeline. This smoke test (a quick check that core functionality works) sends requests through the new public REST API at https://easeia.api.localhost and verifies successful publish responses and no runtime errors.
Quick checklist
- Project: easeia-monorepo
- App: easeia
- Folder: easeia-monorepo
Run a minimal set of calls against the API and check three outcomes: HTTP 200 responses, a queued publish job or confirmation payload, and zero errors in service logs within five minutes. If you use an automated runner, fail the build on non-200 responses or on JSON that lacks the expected publish status field.
How to validate results
Start by issuing the same publish request your pipeline uses and inspect the response body for a publish ID or status flag. Record latency and HTTP code; a successful smoke test typically returns 200 within 2–5 seconds for local environments. Next, confirm the pipeline created the expected artifacts or database entries, and scan the service logs for stack traces or missing-module errors introduced by the rename.
For a live example of a space listing that uses a public API pattern similar to this one, see Bioma Food Hub – Localcine.