mirror of
https://github.com/Orange-OpenSource/hurl.git
synced 2024-09-11 05:35:53 +03:00
Fix case url -> URL.
This commit is contained in:
parent
f25c6b9129
commit
c69ebea464
@ -20,7 +20,7 @@ Enhancements:
|
||||
|
||||
* Support NO_COLOR env variable (https://no-color.org) [#713](https://github.com/Orange-OpenSource/hurl/issues/713)
|
||||
|
||||
* Improve url parsing error message [#662](https://github.com/Orange-OpenSource/hurl/issues/662)
|
||||
* Improve URL parsing error message [#662](https://github.com/Orange-OpenSource/hurl/issues/662)
|
||||
|
||||
* Display deprecated warning when using --progress and --summary option [#637](https://github.com/Orange-OpenSource/hurl/issues/637)
|
||||
|
||||
@ -232,7 +232,7 @@ Changes:
|
||||
|
||||
* Add operators for arithmetic predicates [#210](https://github.com/Orange-OpenSource/hurl/issues/210)
|
||||
|
||||
* Improve error messages if the url contains an illegal character [#207](https://github.com/Orange-OpenSource/hurl/issues/207)
|
||||
* Improve error messages if the URL contains an illegal character [#207](https://github.com/Orange-OpenSource/hurl/issues/207)
|
||||
|
||||
* Improve Error message for the countEquals predicate [#195](https://github.com/Orange-OpenSource/hurl/issues/195)
|
||||
|
||||
@ -362,7 +362,7 @@ Changes:
|
||||
|
||||
Bugs Fixes:
|
||||
|
||||
* Can not parse user in url (Basic Authentication) [#73](https://github.com/Orange-OpenSource/hurl/issues/73)
|
||||
* Can not parse user in URL (Basic Authentication) [#73](https://github.com/Orange-OpenSource/hurl/issues/73)
|
||||
|
||||
* MultipartFormData is not present in json export [#63](https://github.com/Orange-OpenSource/hurl/issues/63)
|
||||
|
||||
|
@ -1,4 +1,4 @@
|
||||
Official hurl bucket url [#289](https://github.com/Orange-OpenSource/hurl/issues/289) :
|
||||
Official Hurl bucket URL [#289](https://github.com/Orange-OpenSource/hurl/issues/289) :
|
||||
- https://github.com/ScoopInstaller/Main/blob/master/bucket/hurl.json
|
||||
|
||||
Update manifest command:
|
||||
|
@ -1,4 +1,4 @@
|
||||
Official hurl manifest url [#324](https://github.com/Orange-OpenSource/hurl/issues/324) :
|
||||
Official hurl manifest URL [#324](https://github.com/Orange-OpenSource/hurl/issues/324) :
|
||||
|
||||
- https://github.com/microsoft/winget-pkgs/tree/master/manifests/o/Orange-OpenSource/Hurl/
|
||||
|
||||
|
@ -296,10 +296,10 @@ Vary: User-Agent
|
||||
Vary: Content-Type
|
||||
```
|
||||
|
||||
### Url assert
|
||||
### URL assert
|
||||
|
||||
Check the last fetched url. This is most meaningful if you have told Hurl to follow redirection (see [`[Options]`section][options] or
|
||||
[`--location` option]). Url assert consists of the keyword `url` followed by a predicate function and value.
|
||||
Check the last fetched URL. This is most meaningful if you have told Hurl to follow redirection (see [`[Options]`section][options] or
|
||||
[`--location` option]). URL assert consists of the keyword `url` followed by a predicate function and value.
|
||||
|
||||
```hurl
|
||||
GET https://example.org/redirecting
|
||||
|
@ -90,10 +90,10 @@ HTTP/1.1 302
|
||||
next_url: header "Location"
|
||||
```
|
||||
|
||||
### Url capture
|
||||
### URL capture
|
||||
|
||||
Capture the last fetched url. This is most meaningful if you have told Hurl to follow redirection (see [`[Options]`section][options] or
|
||||
[`--location` option]). Url capture consists of a variable name, followed by a `:`, and the keyword `url`.
|
||||
Capture the last fetched URL. This is most meaningful if you have told Hurl to follow redirection (see [`[Options]`section][options] or
|
||||
[`--location` option]). URL capture consists of a variable name, followed by a `:`, and the keyword `url`.
|
||||
|
||||
```hurl
|
||||
GET https://example.org/redirecting
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
## Definition
|
||||
|
||||
Request describes an HTTP request: a mandatory [method] and [url], followed by optional [headers].
|
||||
Request describes an HTTP request: a mandatory [method] and [URL], followed by optional [headers].
|
||||
|
||||
Then, [query parameters], [form parameters], [multipart form data], [cookies] and
|
||||
[basic authentication] can be used to configure the HTTP request.
|
||||
@ -91,7 +91,7 @@ alice: secret
|
||||
</div>
|
||||
|
||||
|
||||
[Headers], if present, follow directly after the [method] and [url]. This allows Hurl format to 'look like' the real HTTP format.
|
||||
[Headers], if present, follow directly after the [method] and [URL]. This allows Hurl format to 'look like' the real HTTP format.
|
||||
Contrary to HTTP headers, other parameters are defined in sections (`[Cookies]`, `[QueryStringParams]`, `[FormParams]` etc...)
|
||||
These sections are not ordered and can be mixed in any way:
|
||||
|
||||
@ -135,12 +135,12 @@ Mandatory HTTP request method, one of `GET`, `HEAD`, `POST`, `PUT`, `DELETE`, `C
|
||||
|
||||
### URL
|
||||
|
||||
Mandatory HTTP request url.
|
||||
Mandatory HTTP request URL.
|
||||
|
||||
Url can contain query parameters, even if using a [query parameters section] is preferred.
|
||||
URL can contain query parameters, even if using a [query parameters section] is preferred.
|
||||
|
||||
```hurl
|
||||
# A request with url containing query parameters.
|
||||
# A request with URL containing query parameters.
|
||||
GET https://example.org/forum/questions/?search=Install%20Linux&order=newest
|
||||
|
||||
# A request with query parameters section, equivalent to the first request.
|
||||
@ -150,9 +150,9 @@ search: Install Linux
|
||||
order: newest
|
||||
```
|
||||
|
||||
> Query parameters in query parameter section are not url encoded.
|
||||
> Query parameters in query parameter section are not URL encoded.
|
||||
|
||||
When query parameters are present in the url and in a query parameters section, the resulting request will
|
||||
When query parameters are present in the URL and in a query parameters section, the resulting request will
|
||||
have both parameters.
|
||||
|
||||
### Headers
|
||||
@ -170,7 +170,7 @@ Accept-Encoding: gzip, deflate, br
|
||||
Connection: keep-alive
|
||||
```
|
||||
|
||||
> Headers directly follow url, without any section name, contrary to query parameters, form parameters
|
||||
> Headers directly follow URL, without any section name, contrary to query parameters, form parameters
|
||||
> or cookies
|
||||
|
||||
Note that header usually don't start with double quotes. If the header value starts with double quotes, the double
|
||||
@ -183,15 +183,15 @@ If-Match: "e0023aa4e"
|
||||
|
||||
`If-Match` request header will be sent will the following value `"e0023aa4e"` (started and ended with double quotes).
|
||||
|
||||
Headers must follow directly after the [method] and [url].
|
||||
Headers must follow directly after the [method] and [URL].
|
||||
|
||||
### Query parameters
|
||||
|
||||
Optional list of query parameters.
|
||||
|
||||
A query parameter consists of a field, followed by a `:` and a value. The query parameters section starts with
|
||||
`[QueryStringParams]`. Contrary to query parameters in the url, each value in the query parameters section is not
|
||||
url encoded.
|
||||
`[QueryStringParams]`. Contrary to query parameters in the URL, each value in the query parameters section is not
|
||||
URL encoded.
|
||||
|
||||
```hurl
|
||||
GET https://example.org/news
|
||||
@ -202,7 +202,7 @@ search: {{custom-search}}
|
||||
count: 100
|
||||
```
|
||||
|
||||
If there are any parameters in the url, the resulted request will have both parameters.
|
||||
If there are any parameters in the URL, the resulted request will have both parameters.
|
||||
|
||||
### Form parameters
|
||||
|
||||
@ -223,7 +223,7 @@ number: 33611223344
|
||||
```
|
||||
|
||||
Form parameters section can be seen as syntactic sugar over body section (values in form parameters section
|
||||
are not url encoded.). A [multiline string body] could be used instead of a forms parameters section.
|
||||
are not URL encoded.). A [multiline string body] could be used instead of a forms parameters section.
|
||||
|
||||
~~~hurl
|
||||
# Run a POST request with form parameters section:
|
||||
@ -508,10 +508,8 @@ verbose: true # allow verbose output
|
||||
very-verbose: true # allow more verbose output
|
||||
```
|
||||
|
||||
|
||||
|
||||
[method]: #method
|
||||
[url]: #url
|
||||
[URL]: #url
|
||||
[headers]: #headers
|
||||
[Headers]: #headers
|
||||
[query parameters]: #query-parameters
|
||||
|
@ -94,7 +94,7 @@ So if you want to use typed values (in asserts for instances), you can use `{{my
|
||||
If you're interested in the string representation of a variable, you can surround the variable with double quotes
|
||||
, as in `"{{my_var}}"`.
|
||||
|
||||
> When there is no possible ambiguities, like using a variable in an url, or
|
||||
> When there is no possible ambiguities, like using a variable in an URL, or
|
||||
> in a header, you can omit the double quotes. The value will always be rendered
|
||||
> as a string.
|
||||
|
||||
|
@ -187,7 +187,7 @@ What if we want to follow redirections? We can simply use captures!
|
||||
|
||||
After having created a new quiz, we would like to test the page where the user has been redirected.
|
||||
This is really simple and can be achieved with a [header capture]: on the response to the POST creation request, we
|
||||
are going to capture the [`Location`] header, which indicates the redirection url target, and use it to
|
||||
are going to capture the [`Location`] header, which indicates the redirection URL target, and use it to
|
||||
go to the next page.
|
||||
|
||||
1. Add a new header capture to capture the `Location` header in a variable named `detail_url`:
|
||||
@ -213,9 +213,9 @@ detail_url: header "Location"
|
||||
```
|
||||
|
||||
Captures and asserts can be mixed in the same response spec. For example, we can check that the redirection after
|
||||
the quiz creation matches a certain url, and add a header assert with a matches predicate.
|
||||
the quiz creation matches a certain URL, and add a header assert with a matches predicate.
|
||||
|
||||
2. Add a header assert on the POST response to check the redirection url:
|
||||
2. Add a header assert on the POST response to check the redirection URL:
|
||||
|
||||
```hurl
|
||||
# First, get the quiz creation page to capture
|
||||
|
@ -27,7 +27,7 @@ many tests, the more asserts you write, the less fragile your tests suite will b
|
||||
Now, we want to perform other HTTP requests and keep adding tests. In the same file, we can simply write another
|
||||
request following our first request. Let's say we want to test that we have a [404 page] on a broken link:
|
||||
|
||||
1. Modify `basic.hurl` to add a second request on a broken url:
|
||||
1. Modify `basic.hurl` to add a second request on a broken URL:
|
||||
|
||||
```hurl
|
||||
# Checking our home page:
|
||||
@ -171,9 +171,9 @@ jsonpath "$[0].title" == "What is a pennyroyal?"
|
||||
> mocked data is used and asserts can be tested on known values. Our app could also use
|
||||
> a mocked database, configured in our tests suits.
|
||||
|
||||
Note that the question API use query parameters `offset`, `size` and `sort`, that's why we have written the url with
|
||||
Note that the question API use query parameters `offset`, `size` and `sort`, that's why we have written the URL with
|
||||
query parameters <http://localhost:8080/api/questions?offset=0&size=20&sort=oldest>. We can set the query parameters
|
||||
in the url, or use a [query parameter section].
|
||||
in the URL, or use a [query parameter section].
|
||||
|
||||
4. Use a query parameter section in `basic.hurl`:
|
||||
|
||||
|
@ -76,7 +76,7 @@ container has started, but the application server can take a few seconds to be
|
||||
really ready to accept incoming HTTP requests.
|
||||
|
||||
To do so, we can test our health API. With a function `wait_for_url`,
|
||||
we use Hurl to check a given url to return a `200 OK`. We loop on this function
|
||||
we use Hurl to check a given URL to return a `200 OK`. We loop on this function
|
||||
until the check succeeds. Once the test has succeeded, we stop the container.
|
||||
|
||||
5. Modify `bin/integration.sh` to wait for the application to be ready:
|
||||
|
@ -60,7 +60,7 @@ $ java -jar quiz-0.0.2.jar
|
||||
```
|
||||
|
||||
Either you're using the Docker images or the jar app, you can open a browser and test the quiz application by
|
||||
typing the url <http://localhost:8080>:
|
||||
typing the URL <http://localhost:8080>:
|
||||
|
||||
<div>
|
||||
<img class="light-img" src="/docs/assets/img/quiz-light.png" width="400px" alt="Quiz home page"/>
|
||||
|
Loading…
Reference in New Issue
Block a user