Your progress is only saved in this browser. to protect it and pick up on any device.

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.

0 of 2 steps0%
1

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.

  1. 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):
text
Generate a new local Postman collection named "Artemis Integration Tests" to do an end-to-end integration test of the Artemis API. - Use the "Artemis Mission Control" collection and its example responses for the request types and bodies. - Add afterResponse scripts to chain data between the requests. Chaining must work within a single run of the collection, and later requests use {{apiKey}} as the x-api-key header. - Create an environment "artemis.test" with only baseUrl: https://artemis.up.railway.app. No apiKey, because the flow registers its own crew member. Use a different name and email than mine so my mission is untouched. Flow: 1. Register a new crew member (POST /register) - save api_key & callsign 2. Generate a mission briefing (POST /mission/brief) with phase: transit 3. Get mission overview (GET /mission) 4. Create a mission log (POST /logs) three times - save each log ID (path is response.log.id) Crew: wiseman, glover, koch, hansen Category: navigation, life-support, communication, science, crew-status, anomaly 5. Update a Mission Log (PATCH /logs/{logId1}) - category to science 6. Delete a Mission Log (DELETE /logs/{logId2}) - use a non-anomaly / communication log 7. Generate a mission briefing (POST /mission/brief) with empty body 8. Get mission overview (GET /mission) - all steps completed: true Do not write tests yet, we will add them subsequently. Then run the whole collection against artemis.test to check that every request succeeds, and publish the collection and the environment to my Postman workspace.
  1. Review what the agent created: a new collection folder and postman/environments/artemis.test.environment.yaml.
Note: Do not add tests yet. The next step covers that.

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.

2

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.

  1. Stay in the same agent session, or start a new one, and send this prompt:
text
Add pm.test assertions to every request in the "Artemis Integration Tests" collection, based on the real responses. At minimum assert the status code for each request. Keep the existing chaining logic in the afterResponse scripts. Then run the collection against the artemis.test environment, fix anything that fails and run it again until every assertion passes. Finally sync my work to my Postman workspace.
  1. 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:

text
This test is failing with . Debug it.