You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by as...@apache.org on 2021/01/18 15:03:27 UTC
[camel-k] branch master updated: Fix contributing documentation for
integration test naming convention
This is an automated email from the ASF dual-hosted git repository.
astefanutti pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k.git
The following commit(s) were added to refs/heads/master by this push:
new e74a952 Fix contributing documentation for integration test naming convention
e74a952 is described below
commit e74a952dddf6547672ca3bdb1b302d4cfc76281e
Author: Aurélien Pupier <ap...@redhat.com>
AuthorDate: Mon Jan 18 13:38:14 2021 +0100
Fix contributing documentation for integration test naming convention
Signed-off-by: Aurélien Pupier <ap...@redhat.com>
---
docs/modules/ROOT/pages/developers.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/developers.adoc b/docs/modules/ROOT/pages/developers.adoc
index 865d71b..2a0cda3 100644
--- a/docs/modules/ROOT/pages/developers.adoc
+++ b/docs/modules/ROOT/pages/developers.adoc
@@ -87,7 +87,7 @@ Unit tests are executed automatically as part of the build. They use the standar
Integration tests (aimed at ensuring that the code integrates correctly with Kubernetes and OpenShift), need special care.
-The **convention** used in this repo is to name unit tests `xxx_test.go`, and name integration tests `yyy_integration_test.go`.
+The **convention** used in this repo is to name tests `xxx_test.go`.
Integration tests are all in the https://github.com/apache/camel-k/tree/master/e2e[/e2e] dir.
Since both names end with `_test.go`, both would be executed by go during the build, so you need to put a special **build tag** to mark