eclipse-score / eclipse-score/lifecycle
Mocks for health monitor
- Dominant language
- C++
- Stars
- 6
- Forks
- 34
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 80
Description
### What
All APIs from our public headers shall be mocked
- [health_monitor.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/health_monitor.h).
- [tag.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/tag.h)
- [common.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/common.h)
### Acceptance Criteria (DoD)
- bazel target `health_monitoring_cc` created and mocking all public headers.
- [health_monitor.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/health_monitor.h).
- [tag.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/tag.h)
- [common.h](https://github.com/eclipse-score/lifecycle/blob/main/score/health_monitor/src/cpp/common.h)
### How
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the public APIs in health_monitor.h, tag.h, and common.h. Inspect the existing Bazel definitions around the health monitor to understand how the health_monitoring_cc target should be structured. Done means the target exists and provides mocks for all APIs in those three headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100