Where the Testing, Validation and Results document and the Global Test Registry disagree
The two source documents overlap and are maintained separately. The GTR is the registry of which tests exist and what stage each has reached; the TVR is the narrative plan, and it carries the review comments that are the only per-test commentary the programme has. This page is what falls out of comparing them.
The granularity is the work package, not the test. The TVR has no per-test identifiers, so a finding here names a work package or a section number and never an individual test. Anything finer would be a judgement about the programme's structure rather than a comparison of two documents, and this site does not make those on a source owner's behalf.
Regenerated from 5G-EMERGE_P2_Testing, Validation and Results(TVR)_v3.0.docx as revised
2026-09-24, by the same pass that attaches review comments to the test
status cards. Nothing on this page is maintained by hand.
The TVR plans tests for WP2.2, named by 1 heading(s). The registry has no rows for it at all, so the DBR has no cards to represent it.
Meanwhile Nothing is lost today — no open review comment sits beneath it — but any test the TVR plans here is invisible to the site.
The TVR plans tests for WP2.4, named by 1 heading(s). The registry has no rows for it at all, so the DBR has no cards to represent it.
Meanwhile Nothing is lost today — no open review comment sits beneath it — but any test the TVR plans here is invisible to the site.
The TVR plans tests for WP6.1, named by 1 heading(s). The registry has no rows for it at all, so the DBR has no cards to represent it.
Meanwhile Nothing is lost today — no open review comment sits beneath it — but any test the TVR plans here is invisible to the site.
The TVR plans tests for WP6.3, named by 1 heading(s). The registry has no rows for it at all, so the DBR has no cards to represent it.
Meanwhile Nothing is lost today — no open review comment sits beneath it — but any test the TVR plans here is invisible to the site.
The TVR plans tests for WP6.3.11, named by 1 heading(s). The registry has no rows for it at all, so the DBR has no cards to represent it.
Meanwhile Nothing is lost today — no open review comment sits beneath it — but any test the TVR plans here is invisible to the site.
The TVR names WP6.4.2 in 1 heading(s). The registry has no work package of that name; its nearest is WP6.4.
Meanwhile The comments stay unmatched. Folding WP6.4.2 into WP6.4 would be a judgement about the programme's structure rather than a mapping, and the DBR does not make those on a source's behalf.
The TVR names WP6.4.3 in 1 heading(s). The registry has no work package of that name; its nearest is WP6.4.
Meanwhile The comments stay unmatched. Folding WP6.4.3 into WP6.4 would be a judgement about the programme's structure rather than a mapping, and the DBR does not make those on a source's behalf.
The TVR names WP6.4.4 in 1 heading(s), with 9 open review comment(s) beneath it. The registry has no work package of that name; its nearest is WP6.4.
Meanwhile The comments stay unmatched. Folding WP6.4.4 into WP6.4 would be a judgement about the programme's structure rather than a mapping, and the DBR does not make those on a source's behalf.
2 card(s) under WP3.2.2 carry a TVR Section of "§3.x", which does not name a TVR section. It reads as a reference and resolves to nothing.
Meanwhile Ignored for matching, exactly as an empty value is. The heading-derived work package still places the card, so nothing is lost beyond the narrowing a real section number would have given.
6 card(s) under WP5.3 carry a TVR Section of "See TN 5.3", which does not name a TVR section. It reads as a reference and resolves to nothing.
Meanwhile Ignored for matching, exactly as an empty value is. The heading-derived work package still places the card, so nothing is lost beyond the narrowing a real section number would have given.
4 card(s) under WP3.1.5 carry a TVR Section of §3.4. That section exists, but neither it nor any heading above it names a work package, so the TVR does not attribute it to one.
Meanwhile Ignored for matching. The heading-derived work package places the card; a reference the TVR attributes to nothing cannot narrow it further.
Each finding carries the source data query that owns getting it answered, where one has been raised. A query is a question put to the document's owner — this site never edits a source document, so a divergence stays listed here until the source changes.