This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new aefc036 Fix links in the test infra readme
aefc036 is described below
commit aefc03688b4a515ad753f18d86a4397f327fe2ed
Author: Guillaume Nodet <gno...@gmail.com>
AuthorDate: Tue Jan 5 11:45:30 2021 +0100
Fix links in the test infra readme
---
test-infra/README.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/test-infra/README.md b/test-infra/README.md
index 6d2843a..e5b3b44 100644
--- a/test-infra/README.md
+++ b/test-infra/README.md
@@ -5,7 +5,7 @@
One of the first steps when implementing a new test, is to identify how to
simulate infrastructure required for it to
run. The test-infra module provides a reusable library of infrastructure that
can be used for that purpose.
-In general, the integration test leverages the features provided by the
project https://www.testcontainers.org/[TestContainers]
+In general, the integration test leverages the features provided by the
project [TestContainers](https://www.testcontainers.org/)
and uses container images to simulate the environments. Additionally, it may
also support running the tests against remote
environments as well as, when available, embeddable components. This varies by
each component and it is recommended to
check the code for additional details.
@@ -21,11 +21,11 @@ latency, slow backends, etc).
JUnit 5 manages the lifecycle of the services, therefore each service must be
a JUnit 5 compliant extension. The exact
extension point that a service must extend is specific to each service. The
JUnit 5
-https://junit.org/junit5/docs/current/user-guide/[documentation] is the
reference for the extension points.
+[documentation](https://junit.org/junit5/docs/current/user-guide/) is the
reference for the extension points.
In general, the services should aim to minimize the test execution time and
resource usage when running. As such,
-the
https://junit.org/junit5/docs/5.1.1/api/org/junit/jupiter/api/extension/BeforeAllCallback.html[BeforeAllCallback]
-and
https://junit.org/junit5/docs/5.1.1/api/org/junit/jupiter/api/extension/AfterAllCallback.html[AfterAllCallback]
+the
[BeforeAllCallback](https://junit.org/junit5/docs/5.1.1/api/org/junit/jupiter/api/extension/BeforeAllCallback.html)
+and
[AfterAllCallback](https://junit.org/junit5/docs/5.1.1/api/org/junit/jupiter/api/extension/AfterAllCallback.html)
should be the preferred extensions whenever possible because they allow the
instance of the infrastructure to be static
throughout the test execution.
@@ -43,4 +43,4 @@ to build the service can be provided. The Dockerfile should
try to minimize the
whenever possible.
It is also possible to use embeddable components when required, although this
usually lead to more code and higher
-maintenance.
\ No newline at end of file
+maintenance.
