Connect a Postman API key to check your work
You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.
Generate Integration Test Suite
Have your agent scaffold an end-to-end integration test collection from your Artemis collection, plus a separate test environment. The suite registers its own fresh crew member, so it needs no secret.
- In your agent, start a new session from the repo root so the task has a clean context, then send this prompt (edit it if you need to):
- Review what the agent created: a new collection folder and
postman/environments/artemis.test.environment.yaml.
Troubleshooting: If a request returns 401, the chaining script did not save api_key. Paste the failing output to your agent and ask it to fix the afterResponse scripts. Values set with pm.environment.set last for the run only and are not written back to the environment file.
Run and Verify Tests
Add assertions to every request in the integration collection, then run the suite until it is green and push it. LiftOff checks your cloud workspace for the artemis.test environment and for pm.test assertions in the test collection.
- Stay in the same agent session, or start a new one, and send this prompt:
- Check the agent's final report: every assertion passes and the work is published to your workspace.
See what it wrote. Open the request files in postman/collections/Artemis Integration Tests/: each request now has pm.test assertions at the end of its afterResponse script, after the chaining code.
Debugging tip: If a test fails, paste the error into your agent: