Server status
Server status can be used to monitor the executing instance of Foretify. Use the --enable_status_server invocation option to enable server status updates.
Server status endpoints
Server status exports two endpoints, /version and /status. Its result is in JSON format.
/version - Return the Foretify version.
curl: http://localhost:PORT/version
{"version":"feature/VERSION"}
/status - Return the following attributes of the run:
status- Current status of the run. See Server status values for a list and description of the status values.
runFolder- The run folder of the current run or empty string if the run didn't started yet.
externalJobId- The external job ID if provided on the command line, otherwise, empty string.
seed- The current seed being used.
runId- An incremental counter of runs (when run in batch mode), starting from 1.
runsCountInCluster- Total runs in this batch.
curl: http://localhost:PORT/status
{"status":"NO_LOADED_FILE","runFolder":"","externalJobId":"","seed":1,"runId":1,"runsCountInCluster":1}
Server status values
Following are server status values.
| Name | Description |
|---|---|
| INITIALIZING | Starting runtime process. |
| NO_LOADED_FILE | No file is loaded. |
| LOADING | OSC file being loaded. |
| LOAD_FAILED | Load failed. |
| LOAD_SUCCEED | Load succeeded (in batch mode, this status will be set for a very short period). |
| PLANNING | Generation in process. |
| PLAN_SUCCEED | Generation done (in batch mode, this status will be set for a very short period). |
| RUNNING | Test executing. |
| COMPLETED | Test execution finished succesfully. |
| SUT_ERROR | Test execution finished with SUT error. |
| INCOMPLETE_SCENARIO | Test execution finished with incomplete scenario. |
| CONTRADICTION | Contradiction detected. |
| TEST_ERROR | Test execution finished with some error. |
| RUN_TIMEOUT | Test execution timed out. |
| NOT_EXECUTED | Test execution skipped because of some error. |