root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Fix broken links in Testing chapter

This commit is contained in:
Sam Brannen 2018-09-21 14:45:25 +02:00
parent 2a6da6a623
commit f7263abbf0
2 changed files with 14 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/docs/asciidoc/testing-webtestclient.adoc
View File

@ -1,7 +1,7 @@
[[webtestclient]] [[webtestclient]]
= WebTestClient = WebTestClient
`WebTestClient` is a thin shell around <<web-reactive.adoc#webflux-webclient, WebClient>>, `WebTestClient` is a thin shell around <<web-reactive.adoc#webflux-client, WebClient>>,
using it to perform requests and exposing a dedicated, fluent API for verifying responses. using it to perform requests and exposing a dedicated, fluent API for verifying responses.
`WebTestClient` binds to a WebFlux application by using a `WebTestClient` binds to a WebFlux application by using a
<<testing.adoc#mock-objects-web-reactive,mock request and response>>, or it can test any <<testing.adoc#mock-objects-web-reactive,mock request and response>>, or it can test any
@ -140,9 +140,9 @@ are readily available following `bindToServer`. For all others, you need to use
[[webtestclient-tests]] [[webtestclient-tests]]
== Writing Tests == Writing Tests
`WebTestClient` is a thin shell around <<web-reactive.adoc#webflux-webclient,WebClient>>. `WebTestClient` provides an API identical to <<web-reactive.adoc#webflux-client,WebClient>>
It provides an identical API up to the point of performing a request by using `exchange()`. up to the point of performing a request by using `exchange()`. What follows after
What follows after `exchange()` is a chained API workflow to verify responses. `exchange()` is a chained API workflow to verify responses.
Typically, you start by asserting the response status and headers, as follows: Typically, you start by asserting the response status and headers, as follows:

20
src/docs/asciidoc/testing.adoc
View File

@ -1264,7 +1264,7 @@ programming model in JUnit 5):
* <<integration-testing-annotations-junit-jupiter-springjunitconfig>> * <<integration-testing-annotations-junit-jupiter-springjunitconfig>>
* <<integration-testing-annotations-junit-jupiter-springjunitwebconfig>> * <<integration-testing-annotations-junit-jupiter-springjunitwebconfig>>
* <<integration-testing-annotations-junit-jupiter-enabledif>> * <<integration-testing-annotations-junit-jupiter-enabledif>>
* <<integration-testing-annotations-junit-jupiter=-disabledif>> * <<integration-testing-annotations-junit-jupiter-disabledif>>
@ -1406,7 +1406,7 @@ example, you can create a custom `@EnabledOnMac` annotation as follows:
[[integration-testing-annotations-junit-jupiter=-disabledif]] [[integration-testing-annotations-junit-jupiter-disabledif]]
===== `@DisabledIf` ===== `@DisabledIf`
`@DisabledIf` is used to signal that the annotated JUnit Jupiter test class or test `@DisabledIf` is used to signal that the annotated JUnit Jupiter test class or test
@ -1627,8 +1627,9 @@ configuration of individual JUnit Jupiter based test methods, as follows:
---- ----
==== ====
For further details, see the <<core.adoc#annotation-programming-model,Spring For further details, see the
Annotation Programming Model>>. https://github.com/spring-projects/spring-framework/wiki/Spring-Annotation-Programming-Model[Spring Annotation Programming Model]
wiki page.
@ -1670,9 +1671,8 @@ in turn, manages a `TestContext` that holds the context of the current test. The
and delegates to `TestExecutionListener` implementations, which instrument the actual and delegates to `TestExecutionListener` implementations, which instrument the actual
test execution by providing dependency injection, managing transactions, and so on. A test execution by providing dependency injection, managing transactions, and so on. A
`SmartContextLoader` is responsible for loading an `ApplicationContext` for a given test `SmartContextLoader` is responsible for loading an `ApplicationContext` for a given test
class. See the {api-spring-framework}[Javadoc] and the Spring test suite for further class. See the {api-spring-framework}/test/context/package-summary.html[Javadoc] and the
information and examples of various implementations. Spring test suite for further information and examples of various implementations.
===== `TestContext` ===== `TestContext`
@ -3860,7 +3860,7 @@ of `PlatformTransactionManager` within the test's `ApplicationContext`, you can
qualifier by using `@Transactional("myTxMgr")` or `@Transactional(transactionManager = qualifier by using `@Transactional("myTxMgr")` or `@Transactional(transactionManager =
"myTxMgr")`, or `TransactionManagementConfigurer` can be implemented by an "myTxMgr")`, or `TransactionManagementConfigurer` can be implemented by an
`@Configuration` class. Consult the `@Configuration` class. Consult the
{api-spring-framework}/test/context/transaction/TestContextTransactionUtils.html#retrieveTransactionManager[Javadoc {api-spring-framework}/test/context/transaction/TestContextTransactionUtils.html#retrieveTransactionManager-org.springframework.test.context.TestContext-java.lang.String-[Javadoc
for `TestContextTransactionUtils.retrieveTransactionManager()`] for details on the for `TestContextTransactionUtils.retrieveTransactionManager()`] for details on the
algorithm used to look up a transaction manager in the test's `ApplicationContext`. algorithm used to look up a transaction manager in the test's `ApplicationContext`.
@ -5295,8 +5295,8 @@ when using HTML-based views. This integration lets you:
* Easily test HTML pages by using tools such as * Easily test HTML pages by using tools such as
http://htmlunit.sourceforge.net/[HtmlUnit], http://htmlunit.sourceforge.net/[HtmlUnit],
http://seleniumhq.org/projects/webdriver/[WebDriver], and http://seleniumhq.org/projects/webdriver/[WebDriver], and
http://www.gebish.org/manual/current/testing.html#spock_junit__testng[Geb] without the http://www.gebish.org/manual/current/#spock-junit-testng[Geb] without the need to
need to deploy to a Servlet container. deploy to a Servlet container.
* Test JavaScript within pages. * Test JavaScript within pages.
* Optionally, test using mock services to speed up testing. * Optionally, test using mock services to speed up testing.
* Share logic between in-container end-to-end tests and out-of-container integration tests. * Share logic between in-container end-to-end tests and out-of-container integration tests.