woose/90DaysOfDevOps
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update Day 21 content and affiliations

Browse Source
This commit is contained in:
Oleg Nenashev 2024-01-18 16:29:38 +01:00
parent 4ce3b60733
commit 29e7e81e61
4 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
2024/Images/day07-1.png → 2024/Images/day21-1.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

0
2024/Images/day07-2.png → 2024/Images/day21-2.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 36 KiB

After

Width:  |  Height:  |  Size: 36 KiB

0
2024/Images/day07-3.png → 2024/Images/day21-3.png
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 93 KiB

After

Width:  |  Height:  |  Size: 93 KiB

19
2024/day21.md
View File

@ -1,20 +1,20 @@
# Day 7: Advanced Code Coverage with Jenkins, GitHub and API Mocking
# Day 21: Advanced Code Coverage with Jenkins, GitHub and API Mocking
Presentation by [Oleg Nenashev](https://linktr.ee/onenashev),
Jenkins core maintainer and community builder at WireMock
Jenkins core maintainer, developer advocate and community builder at Gradle
**TL;DR:** I will talk about how modern Jenkins allows you to analyze
**TL;DR:** I will talk about how modern Jenkins allows you to analyze
and improve code coverage with help of the new Coverage Plugin for Jenkins,
support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.),
support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.),
test parallelization, and GitHub Checks API.
We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers.
![Jenkins and GitHub Checks](./Images/day07-1.png)
![Jenkins and GitHub Checks](./Images/day21-1.png)
## Resources
- Video: Coming Soon (January 07)
- Slides: Coming Soon (January 07)
- Video: Coming Soon (January 21)
- [Slides](https://speakerdeck.com/onenashev/advanced-code-coverage-with-jenkins-github-and-api-mocking/) (Premier - January 21)
## Full Abstract
@ -22,7 +22,7 @@ In 2015-2018, I talked about how to use the Jenkins Pipeline and custom librarie
Coverage plugins were rather weak, and one needed some scripts and hacks to make it work, and to DIY for distributed testing. In 2021 the situation has changed significantly thanks to the Coverage and Checks API plugins.
Distributed integration testing also became easier thanks to better coverage collectors and integrations with API mocking tools. So, good time to be alive… and use Jenkins!
![Jenkins and GitHub Checks](./Images/day07-2.png)
![Jenkins and GitHub Checks](./Images/day21-2.png)
We will talk about how modern Jenkins allows you to improve and analyze code coverage.
We will talk about unit and integration testing with WireMock,
@ -32,7 +32,7 @@ parallelization for heavy integration tests and API mocking, and integration wit
How can you analyze code coverage in Jenkins and when do you need to create your own libraries?
And what’s the fuzz about Testcontainers and WireMock for integration testing?
![Jenkins and GitHub Checks](./Images/day07-3.png)
![Jenkins and GitHub Checks](./Images/day21-3.png)
## References
@ -46,3 +46,4 @@ Contribute to open source projects:
[Jenkins](https://www.jenkins.io/participate),
[WireMock](https://wiremock.org/participate),
[Testcontainers](https://java.testcontainers.org/contributing/)
[Gradle](https://gradle.org/resources/)