Update the details of a single test step in Runscope
A documented Runscope operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Update the details of a single test step.
- PUTChanges data · Test Steps
api.runscope.com/buckets/{bucketKey}/tests/{testId}/steps/{stepId}
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Runscope operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Runscope operations
- Create a new bucketPOST · changes data
- Create a messagePOST · changes data
- Create new shared environmentPOST · changes data
- Create a testPOST · changes data
- Clear a bucket (remove all messages)DELETE · changes data
- Add new test stepPOST · changes data
- Create new test environmentPOST · changes data
- Delete a single bucket resourceDELETE · changes data
Questions
- Can HumDay update the details of a single test step in Runscope?
- Yes. This operation is published in Runscope's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Runscope data?
- Yes — this is a PUT operation, so it changes something in Runscope. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Runscope account.
Where this came from
Read from a published API description for Runscope at raw.githubusercontent.com/Runscope/runscope-api-examples/master/schemas/runscope-swagger-v. The description above is the provider’s own wording, not ours. Last published 2023-03-06.