Merge pull request #489 from oleg-nenashev/patch-1

This commit is contained in:
Michael Cade 2024-02-11 13:42:42 +00:00 committed by GitHub
commit aff55d6139
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -9,11 +9,11 @@ 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/day21-1.png)
![Jenkins and GitHub Checks](./Images/day26-1.png)
## Resources
- Video: Coming Soon (January 21)
- [Video Recording](https://www.youtube.com/watch?v=ZBaQ71CI_lI)
- [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/day21-2.png)
![Jenkins and GitHub Checks](./Images/day26-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 whats the fuzz about Testcontainers and WireMock for integration testing?
![Jenkins and GitHub Checks](./Images/day21-3.png)
![Jenkins and GitHub Checks](./Images/day26-3.png)
## References