Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Week5: Demo proposal #2403

Closed
wants to merge 1 commit into from
Closed

Week5: Demo proposal #2403

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions contributions/demo/week5/tianning-peiyang/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# Assignment Proposal

## Title

Automating Code Coverage Analysis in CI Pipeline

## Names and KTH ID

- Tianning Liang ([email protected])
- Peiyang Zheng ([email protected])

## Deadline

- Week 5

## Category

- Demo

## Description

This project aims to integrate a code coverage analysis tool (such as JaCoCo or Emma) into a CI pipeline. The coverage analysis will provide insights into the proportion of code exercised by tests, ensuring the robustness of the application. Additionally, the project will automate the process of saving coverage reports to the cloud, enabling historical comparisons and trend analysis.

Stretch Goal: Automate the entire process using GitHub Actions, ensuring that every code change triggers a coverage analysis and stores the results automatically.

**Relevance**

Code coverage is crucial for assessing the effectiveness of unit tests in covering the codebase. While running tests is essential, it’s equally important to understand which parts of the code are tested and which are not. This helps in identifying untested areas, reducing the risk of bugs. By integrating code coverage into the CI pipeline, we ensure that every change is scrutinized not only for correctness but also for completeness in terms of testing.

Additionally, by storing historical coverage data, teams can track their progress in improving test coverage over time. This historical perspective can be valuable in understanding the impact of refactoring, adding new features, or making other significant changes to the codebase.
Loading