2022-05-31 15:36:54 +03:00
|
|
|
|
# Running Tests
|
|
|
|
|
|
2022-06-10 12:10:58 +03:00
|
|
|
|
## Use --test Option
|
|
|
|
|
|
2022-05-31 15:36:54 +03:00
|
|
|
|
Hurl is run by default as an HTTP client, returning the body of the last HTTP response.
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
$ hurl hello.hurl
|
|
|
|
|
Hello World!
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
When multiple input files are provided, Hurl outputs the body of the last HTTP response of each file.
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
$ hurl hello.hurl assert_json.hurl
|
|
|
|
|
Hello World![
|
|
|
|
|
{ "id": 1, "name": "Bob"},
|
|
|
|
|
{ "id": 2, "name": "Bill"}
|
|
|
|
|
]
|
|
|
|
|
```
|
|
|
|
|
|
2022-06-10 12:10:58 +03:00
|
|
|
|
For testing, we are only interested in the asserts results, we don't need the HTTP body response. To use Hurl as a
|
|
|
|
|
test tool with an adapted output, you can use [`--test` option]:
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
$ hurl --test hello.hurl assert_json.hurl
|
2022-08-23 19:36:47 +03:00
|
|
|
|
[1mhello.hurl[0m: [1;36mRunning[0m [1/2]
|
|
|
|
|
[1mhello.hurl[0m: [1;32mSuccess[0m (6 request(s) in 245 ms)
|
|
|
|
|
[1massert_json.hurl[0m: [1;36mRunning[0m [2/2]
|
|
|
|
|
[1massert_json.hurl[0m: [1;32mSuccess[0m (8 request(s) in 308 ms)
|
2022-06-10 12:10:58 +03:00
|
|
|
|
--------------------------------------------------------------------------------
|
2022-08-23 19:36:47 +03:00
|
|
|
|
Executed files: 2
|
|
|
|
|
Succeeded files: 2 (100.0%)
|
|
|
|
|
Failed files: 0 (0.0%)
|
|
|
|
|
Duration: 561 ms
|
2022-06-10 12:10:58 +03:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Or, in case of errors:
|
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
$ hurl --test hello.hurl error_assert_status.hurl
|
2022-08-23 19:36:47 +03:00
|
|
|
|
[1mhello.hurl[0m: [1;36mRunning[0m [1/2]
|
|
|
|
|
[1mhello.hurl[0m: [1;32mSuccess[0m (6 request(s) in 258 ms)
|
|
|
|
|
[1massert_json.hurl[0m: [1;36mRunning[0m [2/2]
|
|
|
|
|
[1;31merror[0m: [1mAssert status code[0m
|
|
|
|
|
[1;34m-->[0m assert_json.hurl:6:8
|
|
|
|
|
[1;34m|[0m
|
|
|
|
|
[1;34m 6[0m [1;34m|[0m HTTP/* 200
|
|
|
|
|
[1;34m|[0m [1;31m^^^[0m [1;31mactual value is <301>[0m
|
|
|
|
|
[1;34m|[0m
|
2022-06-10 12:10:58 +03:00
|
|
|
|
|
2022-08-23 19:36:47 +03:00
|
|
|
|
[1massert_json.hurl[0m: [1;31mFailure[0m (5 request(s) in 230 ms)
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
Executed files: 2
|
|
|
|
|
Succeeded files: 1 (50.0%)
|
|
|
|
|
Failed files: 1 (50.0%)
|
|
|
|
|
Duration: 499 ms
|
2022-06-10 12:10:58 +03:00
|
|
|
|
```
|
|
|
|
|
|
2022-09-25 13:52:24 +03:00
|
|
|
|
You can use [`--glob` option] to test files that match a given pattern:
|
2022-06-10 12:10:58 +03:00
|
|
|
|
|
|
|
|
|
```shell
|
|
|
|
|
$ hurl --test --glob "test/integration/**/*.hurl"
|
|
|
|
|
```
|
|
|
|
|
|
2022-12-19 23:30:08 +03:00
|
|
|
|
## Generating Report
|
2022-05-31 15:36:54 +03:00
|
|
|
|
|
2022-12-19 23:30:08 +03:00
|
|
|
|
### HTML Report
|
|
|
|
|
|
|
|
|
|
Hurl can generate an HTML report by using the [`--report-html HTML_DIR`] option.
|
2022-05-31 15:36:54 +03:00
|
|
|
|
|
|
|
|
|
If the HTML report already exists, the test results will be appended to it.
|
|
|
|
|
|
2023-07-21 14:54:15 +03:00
|
|
|
|
<div class="picture">
|
2023-07-21 14:28:26 +03:00
|
|
|
|
<img class="u-drop-shadow u-border u-max-width-100" src="/docs/assets/img/hurl-html-report.png" width="670" alt="Hurl HTML Report">
|
2023-07-21 14:54:15 +03:00
|
|
|
|
</div>
|
2022-05-31 15:36:54 +03:00
|
|
|
|
|
|
|
|
|
The input Hurl files (HTML version) are also included and are easily accessed from the main page.
|
|
|
|
|
|
2023-07-21 14:54:15 +03:00
|
|
|
|
<div class="picture">
|
2023-07-21 14:28:26 +03:00
|
|
|
|
<img class="u-drop-shadow u-border u-max-width-100" src="/docs/assets/img/hurl-html-file.png" width="380" alt="Hurl HTML file">
|
2023-07-21 14:54:15 +03:00
|
|
|
|
</div>
|
2022-12-19 23:30:08 +03:00
|
|
|
|
|
|
|
|
|
### JUnit Report
|
|
|
|
|
|
|
|
|
|
A JUnit report can be produced by using the [`--report-junit FILE`] option.
|
|
|
|
|
|
|
|
|
|
If the JUnit file already exists, it will be updated with the new test results.
|
2022-05-31 15:36:54 +03:00
|
|
|
|
|
|
|
|
|
|
2022-06-10 12:10:58 +03:00
|
|
|
|
## Use Variables in Tests
|
|
|
|
|
|
|
|
|
|
To use variables in your tests, you can:
|
|
|
|
|
|
|
|
|
|
- use [`--variable` option]
|
|
|
|
|
- use [`--variables-file` option]
|
|
|
|
|
- define environment variables, for instance `HURL_foo=bar`
|
|
|
|
|
|
2022-09-28 11:24:24 +03:00
|
|
|
|
You will find a detailed description in the [Injecting Variables] section of the docs.
|
2022-06-10 12:10:58 +03:00
|
|
|
|
|
2022-09-02 15:45:54 +03:00
|
|
|
|
[`--output /dev/null`]: /docs/manual.md#output
|
|
|
|
|
[`--test`]: /docs/manual.md#test
|
|
|
|
|
[`--report-html HTML_DIR`]: /docs/manual.md#report-html
|
2022-12-19 23:30:08 +03:00
|
|
|
|
[`--report-junit FILE`]: /docs/manual.md#report-junit
|
2022-09-02 15:45:54 +03:00
|
|
|
|
[`--test` option]: /docs/manual.md#test
|
|
|
|
|
[`--glob` option]: /docs/manual.md#glob
|
|
|
|
|
[`--variable` option]: /docs/manual.md#variable
|
|
|
|
|
[`--variables-file` option]: /docs/manual.md#variables-file
|
2022-09-28 11:24:24 +03:00
|
|
|
|
[Injecting Variables]: /docs/templates.md#injecting-variables
|