UpdateTest

UpdateTest writes the fields the patch carries and leaves the rest alone. The testset is one of them, so carrying another one moves the test; the testset in the alternative path is not read. Pointing the input or answer at a generator makes the data regenerate asynchronously, putting the test back into pending status. The example overrides change only what the statement displays, which is what interactive problems need when the stored input and answer are instructions for the interactor rather than real data; unset_example_input and unset_example_answer drop them, since an absent oneof means the field was not carried.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
string
required
string
required
Body Params
test
object

Fields an update may write; presence is what says a field was carried. Numbered to match the test's own fields, so the two read side by side.

string

only names the test in the alternative path, never read as a value

Response

Language
Credentials
OAuth2
Missing 1 required scope
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json