5G-EMERGE

Working Process

Step-by-step procedures for updating the DBR when source documents change, and regular maintenance activities to keep the system healthy.

For the identity of each source document, see Information Sources. For how to keep local copies current, see Source Sync.

Event-Driven Updates

Source document changes follow a two-phase process. Phase 1 (sync) is manual; Phase 2 (reprocessing) is automated. See Source Sync for full details.

Phase 1 — Sync the cache (manual)

When you know a source document has been updated on SharePoint:

  1. Ensure OneDrive has finished syncing the new file
  2. Run npm run sync from the repo root to copy updated files into the cache

Phase 2 — Automated reprocessing

The 5g-emerge-reprocess scheduled task runs at 09:00 on weekdays. It detects which cache files have changed since the last processing run and automatically:

  • Applies confident updates to status cards (testbed assignments, responsible partners, KPI targets, test nature, TVR references)
  • Flags ambiguous changes (new test cases, rewritten descriptions, architecture changes) for manual review
  • Writes a dated entry to the Source Changelog

After the reprocessing task runs, review the changelog for any items flagged for manual action.

Manual follow-up after reprocessing

Some changes still require human judgement:

On a new TVR release:

  • Review flagged items in the changelog
  • Update Testbeds if test bed descriptions changed substantially
  • Update S2-Component-Testbed-Mapping.xlsx if component tables changed
  • Create new status cards for any new test cases flagged in the changelog
  • Update E2E Scenarios for new E2E scenarios
  • Regenerate: npm run build

On a new SAI release:

  • Review flagged architecture changes in the changelog
  • Update any status cards or reference docs where interface definitions affect test scope or testbed configuration
  • Regenerate: npm run build

On a GTL update:

  • Review flagged items in the changelog
  • Create new status cards for any new test cases
  • Compare against the Global Test Register for gaps
  • Regenerate: npm run build

On a CTM update:

  • Update S2-Component-Testbed-Mapping.xlsx for new deployment confirmations
  • Upgrade P (Planned) entries to ✓ (Confirmed) where components are now deployed

Recording test results

  1. Open the relevant status card in status/S{N}/WP{X.Y}/TS-*.md
  2. Update the following sections:
    • Status Summary — Overall Status, Confidence, Progress %
    • KPI / KPI Targets → KPI Results — record actual measured values
    • Execution Summary — increment test run count, record latest result
    • Findings & Risks — document findings, close resolved risks/blockers
    • Actions & Next Steps — update or close completed actions
  3. Update Last Updated and Version in the Identity section
  4. Regenerate dashboard: npm run build

Regular Maintenance Activities

Validate test coverage

Review whether every test case in the GTL is represented by an entry in a status card or the global test register:

  1. Open the GTL and the relevant strand sheets (S2–S6)
  2. For each test case, confirm it appears in the Global Test Register and that an owning status card exists
  3. Flag any gaps as items in Issues & Roadmap under Open Questions
  4. Where a test case is confirmed missing from the DBR, create or update the relevant status card

Review and revise the source traceability

When any of the following occur, update Source Traceability and the source callout on the affected page:

  • A new reference or planning page is added to the dashboard
  • A new input source (or source version) is introduced
  • Coverage of an existing source is extended to a new page

This ensures the mapping remains a reliable at-a-glance record of traceability between inputs and the dashboard.

Review pending source corrections

Check Issues & Roadmap (Pending Source Corrections table) before beginning any processing session:

  1. Apply any listed corrections when reading the relevant source
  2. When a correction has been made in the upstream source, remove it from the table and note the version it was resolved in

Related Pages