Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add RecordProperty test traceability: score/time_daemon unit tests

Open
  • Is something wrong?
#91 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Quiet
Tech stack
cpp
Domain
testing

Research direction

Start by locating all cc_test targets and unit-test fixtures under score/time_daemon/, then inspect their SetUp() methods and individual tests. Add the four specified RecordProperty entries with valid comp_req__time_daemon__ identifiers, and run bazel run //:docs to confirm there are no broken traceability links.

Written by the indexing model from the issue text.

Description

[!IMPORTANT]
Link the implementing PR to this issue by including Closes #91 in the PR description or commit message.

What

Add RecordProperty traceability metadata to all unit tests in score/time_daemon/ so each test is linked to the requirement it verifies.

Each test fixture must carry in SetUp():

  • RecordProperty("TestType", "requirements-based")
  • RecordProperty("DerivationTechnique", "requirements-analysis")

Each individual test must carry:

  • RecordProperty("Description", "Given ... When ... Then ...")
  • RecordProperty("FullyVerifies", "comp_req__time_daemon__<keyword>") or RecordProperty("PartiallyVerifies", "comp_req__time_daemon__<keyword>")
Acceptance Criteria
  • All cc_test targets under //score/time_daemon/... carry the four required properties
  • comp_req UIDs referenced are valid comp_req__time_daemon__* identifiers
  • bazel run //:docs shows no broken traceability links for score/time_daemon
References
Dominant language
C++
Stars
2
Forks
12
Avg merge
6d 23h
Merged PRs (30d)
17

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/time

All issues in eclipse-score/time

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.