jenkins/sap-jenkins-library
1
0
Fork 0
mirror of https://github.com/SAP/jenkins-library.git synced 2024-12-14 11:03:09 +02:00
Code Issues Releases Activity

Document how to trigger integration tests.

Browse Source
This commit is contained in:
Marcus Holl 2019-03-13 14:28:53 +01:00
parent cf44e18c69
commit fb6edfc233
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
.github/CONTRIBUTING.md vendored
View File

@ -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. 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/<Number of the pull request>. As a result the status `integration-tests` is pushed to github and will be shown in the pull request.
### Documentation ### Documentation
The contract of functionality exposed by a library functionality needs to be documented, so it can be properly used. The contract of functionality exposed by a library functionality needs to be documented, so it can be properly used.