Skip to content

Commit aff55d6

Browse files
authored
Merge pull request MichaelCade#489 from oleg-nenashev/patch-1
2 parents 751b0c2 + 5bb5b9b commit aff55d6

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

2024/day26.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ support for standard formats (Cobertura, JaCoCo, gcov, JUnit, etc.),
99
test parallelization, and GitHub Checks API.
1010
We will also delve into increasing the integration test coverage with help of WireMock and Testcontainers.
1111

12-
![Jenkins and GitHub Checks](./Images/day21-1.png)
12+
![Jenkins and GitHub Checks](./Images/day26-1.png)
1313

1414
## Resources
1515

16-
- Video: Coming Soon (January 21)
16+
- [Video Recording](https://www.youtube.com/watch?v=ZBaQ71CI_lI)
1717
- [Slides](https://speakerdeck.com/onenashev/advanced-code-coverage-with-jenkins-github-and-api-mocking/) (Premier - January 21)
1818

1919
## Full Abstract
@@ -22,7 +22,7 @@ In 2015-2018, I talked about how to use the Jenkins Pipeline and custom librarie
2222
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.
2323
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!
2424

25-
![Jenkins and GitHub Checks](./Images/day21-2.png)
25+
![Jenkins and GitHub Checks](./Images/day26-2.png)
2626

2727
We will talk about how modern Jenkins allows you to improve and analyze code coverage.
2828
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
3232
How can you analyze code coverage in Jenkins and when do you need to create your own libraries?
3333
And what’s the fuzz about Testcontainers and WireMock for integration testing?
3434

35-
![Jenkins and GitHub Checks](./Images/day21-3.png)
35+
![Jenkins and GitHub Checks](./Images/day26-3.png)
3636

3737
## References
3838

0 commit comments

Comments
 (0)