From fb6edfc233c542646e2e9ae31facbc6f4a000f0b Mon Sep 17 00:00:00 2001 From: Marcus Holl Date: Wed, 13 Mar 2019 14:28:53 +0100 Subject: [PATCH] Document how to trigger integration tests. --- .github/CONTRIBUTING.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 8b308b01f..f5a4adc69 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -24,6 +24,9 @@ Generally speaking, you should fork this repository, make changes in your own fo All pipeline library coding _must_ come with automated unit tests. +Beside that we have an integration test suite. This test are not triggered during normal pull request builds. These tests are mandatory before a change can be merged. It is the duty of the team member of the SAP/jenkins-library project to execute these tests. +In order to trigger these test the `HEAD` commit of the branch associated with the PullRequest needs to be pushed under the branch pattern `it/.*` (recommanded naming conventioon `it/. As a result the status `integration-tests` is pushed to github and will be shown in the pull request. + ### Documentation The contract of functionality exposed by a library functionality needs to be documented, so it can be properly used.