In-Progress limit is the maximum number of tests which can be executed in parallel.
This operation allows a specific test to set this global pool behaviour.
+Zero-value is equivalent to stop the clock (no tests will be executed).
+
+Value '-1' means 'no limit' (full parallel). Be careful with resources consumption.
+
**Request body**:
```
Global operation (also at test identifier level is accessible).
+Zero-value is equivalent to stop the clock (no tests will be executed).
+
+Value '-1' means 'no limit' (full parallel). Be careful with resources consumption.
+
+Defaults to '-2' (no '-1' which is default for *testid-ip-limit* version), which wil show the current pool *ip-limit* and also the number of test cases which are *in progress*.
+
**Request body**:
```
```
{
"result":"<true or false>",
- "response":"<response>"
+ "response":"<base64-encoded output>"
}
```
```
{
- "result":"<true or false>",
+ "result":"<true: if state is 'Success' or false>",
"response":"<response>"
}
```
#### POST /test-interact
+Makes interactive a specific test case id. The amount of 0, implies no execution steps margin, which could be useful to 'freeze' a test in the middle of its execution. Value -1 makes it non-interactive resuming it from the current step.
+
**Request body**:
```
```
{
- "type":"<soft|hard>"
- [,"id":[test identifier (integer: apply to all the tests (-2))]]
+ ["type":"<[soft]|hard>"]
+ [,"id":[test identifier (integer: apply to all the tests (-1))]]
}
```
#### POST /test-junit
+As it could be very large, it will be dumped on provided target directory, '*/tmp/junit.xml*' by default.
+
**Request body**:
```
{
- "targetFile":"<file path>"
+ ["targetFile":"<file path>"]
}
```
```
{
"result":"<true or false>",
- "response":"<response>"
+ "response":"<base64-encoded output>"
}
```
```
{
"result":"<true or false>",
- "response":"<response>"
+ "response":"<base64-encoded output>"
}
```
```
{
"result":"<true or false>",
- "response":"<response>"
+ "response":"<base64-encoded output>"
}
```