letsencrypt / letsencrypt/boulder
logging: ensure unit test coverage of all BRs-required audit events
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Our unit tests use blog.MockLog.GetAll and .GetAllMatching to ensure that certain information was included in log messages. However, our usage of these helpers is inconsistent; in particular, we do not have any unit tests which inspect the log output of boulder-ca. We need to increase our unit test coverage of these audit log messages.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate existing unit tests using blog.MockLog.GetAll and GetAllMatching, then inspect how audit events are checked across the repository. Focus on boulder-ca, where the issue reports no log-output coverage. Done means consistent tests cover all BRs-required audit events, including boulder-ca output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100