From b209b87e61965f700974d0eaf339884ddd0eb12a Mon Sep 17 00:00:00 2001 From: Stanislav Ovchar Date: Sat, 7 Dec 2019 20:35:36 +0300 Subject: [PATCH 1/2] Add links to projects with demo ans examples --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index 0a387226..43771f5d 100644 --- a/README.md +++ b/README.md @@ -455,3 +455,10 @@ You may find some incoherence in that level. JenkinsPipelineUnit aims to help devops code and test Jenkins pipelines with a shorter development cycle. It addresses some of the requirements traced in [JENKINS-33925](https://issues.jenkins-ci.org/browse/JENKINS-33925). If you are willing to contribute please don't hesitate to discuss in issues and open a pull-request. + +## Demos and Examples +* https://github.com/macg33zr/pipelineUnit +* https://github.com/mkobit/jenkins-pipeline-shared-library-example +* https://github.com/SpencerMalone/JenkinsPipelineIntegration +* https://github.com/stchar/pipeline-sharedlib-testharness +* https://github.com/stchar/pipeline-dsl-seed \ No newline at end of file From 87c2463ab4dfc9fa7d36f1acedac735be0f1fc3e Mon Sep 17 00:00:00 2001 From: Stanislav Ovchar Date: Fri, 13 Dec 2019 18:48:26 +0300 Subject: [PATCH 2/2] Add details about project with examples * Add TOC * Add some details about project with examples --- README.md | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 43771f5d..0aef45b4 100644 --- a/README.md +++ b/README.md @@ -13,6 +13,14 @@ you already know that pipeline code is very powerful but can get pretty complex. This testing framework lets you write unit tests on the configuration and conditional logic of the pipeline code, by providing a mock execution of the pipeline. You can mock built-in Jenkins commands, job configurations, see the stacktrace of the whole execution and even track regressions. +# Table of Contents +1. [Usage](#usage) +1. [Configuration](#configuration) +1. [Testing Shared Libraries](#testing-shared-libraries) +1. [Note On CPS](#note-on-cps) +1. [Contributing](#contributing) +1. [Demos and Examples](#demos-and-examples) + ## Usage ### Add to your project as test dependency @@ -457,8 +465,10 @@ It addresses some of the requirements traced in [JENKINS-33925](https://issues.j If you are willing to contribute please don't hesitate to discuss in issues and open a pull-request. ## Demos and Examples -* https://github.com/macg33zr/pipelineUnit -* https://github.com/mkobit/jenkins-pipeline-shared-library-example -* https://github.com/SpencerMalone/JenkinsPipelineIntegration -* https://github.com/stchar/pipeline-sharedlib-testharness -* https://github.com/stchar/pipeline-dsl-seed \ No newline at end of file +| URL | Frameworks and Tools | Test Subject | Test Layers | +|-----|----------------------|--------------|-------------| +| https://github.com/macg33zr/pipelineUnit | Spock, Gradle(Groovy) | JenkinsFile, scripted pipeline, SharedLibrary | UnitTest | +| https://github.com/mkobit/jenkins-pipeline-shared-library-example | Spock, Gradle (Kotlin), Junit | SharedLibrary | Integration, Unit| +| https://github.com/stchar/pipeline-sharedlib-testharness | Junit, Gradle(Groovy) | SharedLibrary | Integration, Unit | +| https://github.com/stchar/pipeline-dsl-seed | Junit, Spock, Gradle(Groovy) | scripted pipeline | Integration(jobdsl), Unit | +| https://github.com/SpencerMalone/JenkinsPipelineIntegration | Spock, Gradle(Groovy) | SharedLibrary | Integration |