Skip to content

Commit

Permalink
Add missing highlights in documentation (#2025)
Browse files Browse the repository at this point in the history
* Update broken code highlight

* fix groovy highlight

Co-authored-by: attilapapai <attila@fake.com>
  • Loading branch information
attilapapai and attilapapai committed Jan 31, 2021
1 parent beb6105 commit 9fa5066
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions doc/matchers/ktor.md
Expand Up @@ -12,7 +12,7 @@ The following matchers are used when testing via the ktor server testkit.
| ---------- | --- |
| `shouldHaveStatus(HttpStatusCode)` | Tests that the response had the given http status code |
| `shouldHaveContent(content)` | Tests that the response has the given body |
| `shouldHaveContentType(ContentType) | Tests that the response has the given Content Type |
| `shouldHaveContentType(ContentType)` | Tests that the response has the given Content Type |
| `shouldHaveHeader(name, value)` | Tests that the response included the given name=value header |
| `shouldHaveCookie(name, value)` | Tests that the response included the given cookie |

Expand All @@ -23,6 +23,6 @@ The following matchers can be used against responses from the ktor http client.
| Matcher | Description |
| ---------- | --- |
| `shouldHaveStatus(HttpStatusCode)` | Tests that the response had the given http status code |
| `shouldHaveContentType(ContentType) | Tests that the response has the given Content Type |
| `shouldHaveContentType(ContentType)` | Tests that the response has the given Content Type |
| `shouldHaveHeader(name, value)` | Tests that the response included the given name=value header |
| `shouldHaveVersion(HttpProtocolVersion)` | Tests that the response used the given protocol version |
4 changes: 2 additions & 2 deletions documentation/docs/quick_start.mdx
Expand Up @@ -121,7 +121,7 @@ And then add the Kotest JUnit5 runner to your dependencies section.
</TabItem>
<TabItem value="Android">

:::info
:::info
Currently, only JVM tests are officially supported in Kotest. Experimental support for instrumented and Robolectric tests is currently under work.

The following steps enable Kotest to be used for unit and integration tests, where the Android framework is not needed or is mocked that usually reside in the
Expand Down Expand Up @@ -178,7 +178,7 @@ For example, the JDBC matchers only work for JVM since JDBC is a Java library.

Add the following dependency to your build:

```
```groovy
testImplementation 'io.kotest:kotest-assertions-core:$version'
```

Expand Down

0 comments on commit 9fa5066

Please sign in to comment.