-
Notifications
You must be signed in to change notification settings - Fork 3
Test 01 03
Bruno Garcia edited this page Feb 12, 2021
·
3 revisions
| Test Case Name | Experiment execution | Test Case id | Test-01-03 |
|---|---|---|---|
| Test Purpose | Verify that the ELCM is able to run experiments | ||
| Configuration | |||
| Test Tool |
curl-like tool, Web browser |
||
| Metric | |||
| References | |||
| Applicability | ELCM | ||
| Pre-test conditions | Test-01-02 has been completed successfully | ||
| Test sequence | Step | From the Additional Resources section below, download descriptor.json
|
|
| Step | Using curl, or a similar tool, send the contents of the file as a json payload to the api/v0/run endpoint of the ELCM. For curl the command is: curl -X POST -d @descriptor.json -H "Content-Type: application/json" <ELCM_Address>/api/v0/run
|
The reply is: {"ExecutionId":<Execution_Number>}
|
|
| Step | In the ELCM dashboard, check if the experiment is running. If it has already finished, check the History tab and look for the <Execution_Number> entry. |
||
| Step | Review the experiment's execution logs to ensure that no unexpected errors appear. | ||
| Step | Using curl or the web browser, access to the execution/<Execution_Number>/logs endpoint |
The same log contents, but in JSON format should appear. | |
| Test Verdict | If no unexpected issues arise, then the ELCM is able to run experiments | PASS | |
| Additional Resources | descriptor.json |