From 88da4f7e6604f0d9a70dfb4d3cf9b49acb6729bb Mon Sep 17 00:00:00 2001 From: xLitil Date: Thu, 3 Apr 2025 11:03:30 +0200 Subject: [PATCH] Update testing.adoc Signed-off-by: xLitil --- spring-batch-docs/modules/ROOT/pages/testing.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-batch-docs/modules/ROOT/pages/testing.adoc b/spring-batch-docs/modules/ROOT/pages/testing.adoc index 7030be5005..1c07466e9f 100644 --- a/spring-batch-docs/modules/ROOT/pages/testing.adoc +++ b/spring-batch-docs/modules/ROOT/pages/testing.adoc @@ -3,8 +3,8 @@ = Unit Testing As with other application styles, it is extremely important to unit test any code written -as part of a batch job. The Spring core documentation covers how to unit and integration -test with Spring in great detail, so it is not be repeated here. It is important, however, +as part of a batch job. The Spring core documentation covers link:$$https://docs.spring.io/spring-framework/reference/testing.html$$[how to unit and integration +test]. with Spring in great detail, so it is not be repeated here. It is important, however, to think about how to "`end to end`" test a batch job, which is what this chapter covers. The `spring-batch-test` project includes classes that facilitate this end-to-end test approach.