Library core: test evidence

Every requirement of this module, the tests named for it, and what each test recorded the last time the evidence was rebuilt.

Requirements
85
Tests named for them
146 124 unit · 22 browser
Result
pass every test passing
Screenshots
6
Recorded
2026-10-09 12:12 UTC
Environment
linux 6.17.0-1022-azure · node v22.23.3 · playwright 1.61.1 · chromium 149.0.7827.55

The requirements are the rows of the module’s requirement matrix. A test is named for a requirement by starting its name with the requirement’s ID. The results are read from the committed evidence set; continuous integration reruns every test and fails when the committed set no longer matches.

Requirements and their tests

85 requirements · 146 tests

RequirementTests and evidence
CORE-BUILD-001pass

The build writes a script-tag bundle to dist/bio.viz-{version}/bio.viz.js that defines the global BioViz.

  • pass unit bio.viz core CORE-BUILD-001: the committed IIFE bundle defines the global BioViz (#1)
CORE-BUILD-002pass

The build writes an ES module bundle to dist/bio.viz-{version}/bio.viz.esm.js with the same exports as the script-tag bundle.

  • pass unit bio.viz core CORE-BUILD-002: the committed ESM bundle has the same exports as the IIFE bundle (#1)
CORE-API-001pass

version equals the version field of package.json: in the source, in both committed bundles, and as BioViz.version on a page that loads the script-tag bundle.

  • pass browser CORE-API-001: a page that loads the committed bundle reads BioViz.version as the package version (#1)
  • pass unit bio.viz core CORE-API-001: BioViz.version in the committed IIFE bundle equals the package version (#1)
  • pass unit bio.viz core CORE-API-001: src/main.js exports version equal to the package version (#1)
  • pass unit bio.viz core CORE-API-001: version in the committed ESM bundle equals the package version (#1)
CORE-DEP-001pass

package.json declares no runtime dependencies: safety.viz and webR are loaded beside the bundle on a page and are never bundled into it.

  • pass unit bio.viz core CORE-DEP-001: package.json declares no runtime dependencies (#1)
CORE-SITE-001pass

The site's home page names the library and its version, and shows the version reported by the bundle that page loaded.

  • pass browser CORE-SITE-001: the home page names the library and its version, and shows the version its bundle reports (#1)
  • pass unit site pages CORE-SITE-001: the home page names the library and its version (#1)
CORE-SITE-002pass

The site's home page holds at a 390-pixel-wide viewport with no horizontal scroll.

  • pass browser CORE-SITE-002: the home page holds at a 390px-wide viewport with no horizontal scroll (#1)
CORE-DATA-001pass

The synthetic biomarker study is vendored as three files in site/data/synthetic-study/ (synthetic_results.csv, synthetic_participants.csv, synthetic_outcomes.csv) with a source record, SOURCE.json, beside them that names the gsm.bio repository, the commit the files were copied from and each file's path there.

  • pass unit the vendored synthetic study CORE-DATA-001: the three files are in site/data/synthetic-study/ with a record naming the gsm.bio commit and each file there (#7)
CORE-DATA-002pass

Each vendored file matches its entry in the source record: the SHA-256 checksum, the size in bytes, the column names and the row count. A file that is changed, missing, or present but not recorded fails the check, as does a record edited without its file.

  • pass unit the vendored synthetic study CORE-DATA-002: each vendored file matches its recorded checksum, size, columns and row count (#7)
  • pass unit vendoring: the copy and its check CORE-DATA-002: a changed file fails the check, even by one character (#7)
  • pass unit vendoring: the copy and its check CORE-DATA-002: a missing file, an unrecorded file and a missing record each fail the check (#7)
  • pass unit vendoring: the copy and its check CORE-DATA-002: a record edited without its file fails the check (#7)
CORE-DATA-003pass

The results table has the columns USUBJID, VISIT, VISITNUM, TEST, STRESU, STRESN and 11,472 rows, one per participant, biomarker and visit: 200 participants, twelve biomarkers, and the visits Baseline, Week 2, Week 4, Week 8 and Week 12.

  • pass unit the vendored synthetic study CORE-DATA-003: the results table has its six columns and 11,472 rows, one per participant, biomarker and visit (#7)
CORE-DATA-004pass

The participant table has the columns USUBJID, ARM, SEX, AGE, BMIBL, RESPONSE and 200 rows, one per participant, and every participant in the results table is in it.

  • pass unit the vendored synthetic study CORE-DATA-004: the participant table has its six columns and 200 rows, one per participant, covering everyone in the results (#7)
CORE-DATA-005pass

The outcomes table has the columns USUBJID, PARAMCD, PARAM, AVAL, CNSR and 200 rows, one per participant and endpoint, and every participant in it is in the participant table.

  • pass unit the vendored synthetic study CORE-DATA-005: the outcomes table has its five columns and 200 rows, one per participant and endpoint, all of them known participants (#7)
CORE-DATA-006pass

Vendoring is a copy: each file is written exactly as gsm.bio holds it at the recorded commit, with the checksum of those bytes recorded. Nothing is retyped, reordered or regenerated, and a second check fails when a vendored file differs from gsm.bio's file at that commit.

  • pass unit vendoring: the copy and its check CORE-DATA-006: a record is refused without the full commit it was copied from (#7)
  • pass unit vendoring: the copy and its check CORE-DATA-006: the check against the source fails when a vendored file differs from the commit it names (#7)
  • pass unit vendoring: the copy and its check CORE-DATA-006: the copy writes each file exactly as the source holds it and records the checksum of those bytes (#7)
CORE-SITE-003pass

The gallery page lists every chart the registry marks available, each with links to its evidence page and its API reference. When no chart is available it says that no chart is published yet.

  • pass browser CORE-SITE-003: the gallery is reached from the home page and lists the published charts, or says that none is published yet (#7)
  • pass unit gallery CORE-SITE-003: a chart that is registered but not yet available is not listed as published (#7)
  • pass unit gallery CORE-SITE-003: a chart’s card shows its picture once that screenshot is committed, and no picture before (#9)
  • pass unit gallery CORE-SITE-003: a registered chart is listed under Charts with links to its evidence page and API reference (#7)
  • pass unit gallery CORE-SITE-003: with no chart registered the gallery says that no chart is published yet (#7)
Screenshot captured by a test of CORE-SITE-003: gallery
CORE-SITE-004pass

The gallery page lists the library's shared parts, each with links to its evidence page and its API reference.

  • pass browser CORE-SITE-004: the gallery lists each shared part, and its two links lead to that module’s evidence page and API reference (#7)
  • pass unit gallery CORE-SITE-004: each shared part is listed with links to its evidence page and API reference (#7)
  • pass unit gallery CORE-SITE-004: the registry as committed lists the core and the connection to R as shared parts (#7)
CORE-SITE-005pass

Every module in the registry (site/config.json) says whether it is a chart or a shared part and names its requirement matrix and its API reference. The site build refuses an entry that does not.

  • pass unit module registry CORE-SITE-005: an entry that does not say whether it is a chart or a shared part is refused (#7)
  • pass unit module registry CORE-SITE-005: an entry without its matrix or its API reference is refused, as is a name registered twice (#7)
  • pass unit module registry CORE-SITE-005: the registry as committed is well formed (#7)
CORE-SITE-006pass

Each module has an evidence page that lists every requirement in its matrix with the requirement's text, the tests named for it and the result each test recorded. A requirement with no test says so.

  • pass browser CORE-SITE-006: every module has an evidence page that lists each requirement of its matrix (#7)
  • pass browser CORE-SITE-006: the connection to R’s evidence page lists every RCON- and PVAL- requirement with the tests that prove it (#7)
  • pass unit evidence page CORE-SITE-006: a requirement with no test says so, and the summary counts it (#7)
  • pass unit evidence page CORE-SITE-006: each requirement shows the tests named for it, unit or browser, with the result each recorded (#7)
  • pass unit evidence page CORE-SITE-006: every requirement is listed in the matrix’s order with its text (#7)
  • pass unit evidence page CORE-SITE-006: tests that carry none of the module’s requirements are listed apart, as run with every module (#7)
  • pass unit evidence page CORE-SITE-006: with every requirement tested and passing the summary says every test is passing (#7)
Screenshot captured by a test of CORE-SITE-006: a requirement and its tests
CORE-SITE-007pass

An evidence page shows, under a requirement, each screenshot a test captured for it. The site build fails when the evidence set names a screenshot that is not committed.

  • pass browser CORE-SITE-007: a screenshot a test captured is shown under its requirement on the evidence page (#7)
  • pass unit evidence page CORE-SITE-007: a screenshot is shown under the requirement it was captured for, and only there (#7)
  • pass unit evidence page CORE-SITE-007: the build is told of a screenshot the evidence names that is not committed (#7)
CORE-SITE-008pass

An evidence page says when its results were recorded and in what environment, and links the continuous-integration run when there was one.

  • pass unit evidence page CORE-SITE-008: results recorded on a developer’s machine say so, and absent provenance is not invented (#7)
  • pass unit evidence page CORE-SITE-008: the page says when and where the results were recorded and links the run (#7)
CORE-SITE-009pass

Each module has an API reference page rendered from the module's one reference file in docs/: its headings, paragraphs, lists, tables and code, with a list of its sections.

  • pass browser CORE-SITE-009: every module has an API reference page that documents each name it exports (#7)
  • pass browser CORE-SITE-009: the connection to R’s API reference documents createConnection and formatStatistic (#7)
  • pass unit API reference page CORE-SITE-009: a link to another reference file goes to that module’s page, and the page names the file it was rendered from (#7)
  • pass unit API reference page CORE-SITE-009: the page is the reference file, rendered: its title, sections, tables and code (#7)
  • pass unit API reference page CORE-SITE-009: the sections are listed at the top, each linked to its place on the page (#7)
  • pass unit markdown: blocks CORE-SITE-009: a fenced block is code, escaped and left as written, and a # inside it is not a heading (#7)
  • pass unit markdown: blocks CORE-SITE-009: a table keeps each column heading on every cell, so it can restack on a narrow screen (#7)
  • pass unit markdown: blocks CORE-SITE-009: headings get the anchors GitHub gives them, repeated ones numbered (#7)
  • pass unit markdown: blocks CORE-SITE-009: paragraphs join their lines, and bullet and numbered lists keep theirs apart (#7)
Screenshot captured by a test of CORE-SITE-009: sections of the reference
CORE-SITE-010pass

The site build fails when an API reference has drifted from the code: an export of the bundle that no reference documents, a function a reference documents that the bundle does not export, a parameter documented in the source that the reference leaves out, or a constant whose value the reference does not give.

  • pass unit API reference: held to the code CORE-SITE-010: a constant whose value the reference does not give is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a function the reference documents that the bundle does not export is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a namespace in the surface stands for each of its members, and a constant carries its value (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a parameter the source documents and the reference leaves out is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: a reference that documents every export, parameter and constant has no problems (#7)
  • pass unit API reference: held to the code CORE-SITE-010: an export no module claims, a surface the bundle lacks and an empty surface are each a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: an export with no heading in the reference is a problem (#7)
  • pass unit API reference: held to the code CORE-SITE-010: the committed references document everything the committed bundle exports (#7)
  • pass unit API reference: held to the code CORE-SITE-010: the connection’s reference is held to the parameters its source documents (#7)
CORE-SITE-011pass

Every requirement row has at least one test named for it, and no test names a requirement that is in no matrix. The evidence run fails otherwise.

  • pass unit evidence normalizer CORE-SITE-011: a requirement row with no test named for it is reported (#7)
  • pass unit evidence normalizer CORE-SITE-011: a test that names a requirement in no matrix is reported with the test (#7)
CORE-SITE-012pass

The gallery page holds at a 390-pixel-wide viewport with no horizontal scroll.

  • pass browser CORE-SITE-012: the gallery holds at a 390px-wide viewport with no horizontal scroll (#7)
CORE-SITE-013pass

A module's evidence page holds at a 390-pixel-wide viewport with no horizontal scroll.

  • pass browser CORE-SITE-013: each module’s evidence page holds at a 390px-wide viewport with no horizontal scroll (#7)
CORE-SITE-014pass

A module's API reference page holds at a 390-pixel-wide viewport with no horizontal scroll; a table is restacked as a list rather than scrolled sideways.

  • pass browser CORE-SITE-014: each module’s API reference holds at a 390px-wide viewport, with its tables restacked (#7)
CORE-SITE-015pass

The site publishes the vendored synthetic study at data/synthetic-study/ with its source record, and the gallery page says what each table holds, how many rows it has and which gsm.bio commit it was copied from.

  • pass browser CORE-SITE-015: the site serves the synthetic study, and the gallery gives its row counts and the commit it was copied from (#7)
  • pass unit gallery CORE-SITE-015: the gallery says what each table of the synthetic study holds, its rows, and the commit it was copied from (#7)
CORE-SITE-016pass

A chart registered as experimental is published with an Experimental badge and the reason (statusNote), on its gallery card, on the home page and on its live demo; the registry refuses one without a reason, refuses a reason on any other module, names a published chart's own status when it lacks a demo, and the committed registry gives the status to the stratified survival chart alone.

  • pass unit gallery CORE-SITE-016: a chart registered as experimental is published with an Experimental badge and the reason, on its gallery card, on the home page and on its live demo; the committed registry gives the stratified survival chart that status (#78)
CORE-SITE-017pass

Every committed evidence picture, the gallery's among them, has a record of the versions of bio.viz it draws, read as text when the picture was written, and each is the package's version as the footnote says it; the record holds the picture's sha256, so a picture swapped in from another commit fails however few of its pixels differ; a capture that shows other pictures (the gallery's page) names them, and each has its own record; no record is left without its picture. The browser suite fails a capture whose page now draws another version than the one kept, and update-baselines-all rewrites every picture and its record.

  • pass unit evidence pictures: the version each one draws CORE-SITE-017: every committed evidence picture, the gallery’s among them, has the record of the versions of bio.viz it draws, each the package’s version as the footnote says it, written for its own bytes (sha256), with the pictures it shows named; no record is left without its picture (#78)
CORE-SITE-018pass

safety.viz's site stylesheet and page shell are vendored as two files in site/vendor/safety.viz-site/ (site.css, shell.html) with a source record, SOURCE.json, beside them that names the safety.viz repository, its dev branch, the commit the files were copied from, and each file's path there, checksum and size. The copy matches its record; a file that is changed, missing, or beside one the record does not name fails the check, and a second check fails when a file differs from safety.viz's at the recorded commit.

  • pass unit the copied site styles CORE-SITE-018: a copied file that is changed, missing, or beside one the record does not name fails the check, and the second check holds each file to safety.viz at the recorded commit (#91)
  • pass unit the copied site styles CORE-SITE-018: safety.viz’s site stylesheet and page shell are in site/vendor/safety.viz-site/ with a record naming the repository, its dev branch, the commit and each file, and the copy matches its record (#91)
CORE-SITE-019pass

Every page of the site loads safety.viz's stylesheet as it was copied, published with its source record, and after it the site's own stylesheet, which redefines none of safety.viz's tokens, writes every colour and typeface as one of them, and styles no class the pages do not write. Every class a page writes is styled by one of the two. On a demo page the site's own stylesheet stops at the chart: no rule of it names an element by its tag alone, but the one on the page's body that wraps a long string, which is switched off again inside the chart, and a chart's parts wrap as the chart has them. The site build fails when the copied stylesheet no longer matches its record.

  • pass browser CORE-SITE-019: every page is styled by safety.viz’s stylesheet as it was copied, published with its record, and then by the site’s own (#91)
  • pass browser CORE-SITE-019: the gallery’s cards, a module’s tabs, the fact panel, the evidence table and the reference’s sidebar are drawn by safety.viz’s rules (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: every class a page writes is styled by one of the two stylesheets, and the site’s own styles no class the pages do not write (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: every page loads the copied stylesheet and then the site’s own, by paths that hold at any depth (#91)
  • pass unit the pages and the two stylesheets CORE-SITE-019: the site’s own stylesheet redefines none of safety.viz’s tokens, writes every colour and typeface as one of them, and names no element by its tag alone but the page’s body (#91, #112)
CORE-SITE-020pass

Every page carries safety.viz's header and footer: the library's name and version, a Gallery entry that opens a list of every published chart, each leading to that chart's live demo, and links to the R check page, safety.viz's site, the repository and the roadmap. Every link in the header leads somewhere, and the page a reader is on is marked in it. The page shell's header, footer and navigation classes are the copied shell's, and its header script is the copied shell's, character for character.

  • pass browser CORE-SITE-020: every page carries the header and the footer: the name and version, a Gallery list of every published chart, and links that all lead somewhere (#91)
  • pass browser CORE-SITE-020: the Gallery list opens from its button and from the keyboard, leads to a chart’s live demo, and the header marks the page a reader is on (#91)
  • pass unit the page shell CORE-SITE-020: the header’s Gallery entry lists each published chart, leading to its live demo, and is a plain link while none is published (#91)
  • pass unit the page shell CORE-SITE-020: the shell’s header, navigation and footer are the copied shell’s, and its header script is the copied shell’s, character for character (#91)
Screenshot captured by a test of CORE-SITE-020: the gallery listScreenshot captured by a test of CORE-SITE-020: the header
CORE-SITE-021pass

The header holds at a 390-pixel-wide viewport with no horizontal scroll, on every kind of page, and the Gallery list opens directly under it, within the screen, and the page still holds with the list open.

  • pass browser CORE-SITE-021: the header holds at a 390px-wide viewport on every kind of page, and the Gallery list opens under it, on the screen (#91)
Screenshot captured by a test of CORE-SITE-021: the header on a phone
CORE-SITE-022pass

A row of the evidence table is laid out by its own words. The table’s two columns are three fifths and two fifths of its width on every module’s page, set and not fitted to what the table holds, so a requirement’s row keeps its columns when a test is added to, or taken from, another requirement.

  • pass browser CORE-SITE-022: a row of the evidence table is laid out by its own words: the two columns are three fifths and two fifths of the table on every module’s page, and a row keeps its columns when another row is given a test with a long name (#85)
CORE-SITE-023pass

A module's card, on the gallery and on the home page, says what the module is in the registry's card text and not in its fuller blurb, which stays at the head of a chart's live demo. A card is at most two sentences and 200 characters: the registry as committed holds every module to it, and the site build refuses an entry with no card text or one past either limit. The group comparison's card names its trend tiles, its picture across the visits and its single visit.

  • pass unit gallery CORE-SITE-023: a card says what its module is in the registry’s card text, at most two sentences and 200 characters, on the gallery and on the home page, and not in the fuller text, which stays at the head of a chart’s live demo; the registry as committed holds every module to it, and the group comparison’s card names its tiles, its picture over time and its single visit (#96)
  • pass unit gallery CORE-SITE-023: the registry refuses an entry with no card text, with more than two sentences, or with more than 200 characters (#96)
CORE-SITE-024pass

In the built site, every card on the gallery and on the home page prints its module's card text, at most two sentences and no more than five lines at 1280 pixels wide; with the first row of charts scrolled to the top of a 1280 by 800 window, the second row's pictures are whole inside the window, which is what is measured: the second row's text and links are not held to be in it; and a chart's fuller text is at the head of its live demo.

  • pass browser CORE-SITE-024: on the gallery and the home page every card says what its module is in the registry’s card text, at most two sentences and five lines at 1280px; with the first row of charts at the top of a 1280 by 800 window the second row’s pictures are in it; and a chart’s fuller text is at the head of its live demo (#96)
CORE-VAR-001pass

A variable is written one way wherever one is taken, an axis, a group, a colour or a panel: a biomarker at a visit with a value type, { measure, visit, value }, or a column, { col }. The value types are raw, baseline, change, fold_change and percent_change, and raw when none is given. variable() returns the variable in full.

  • pass unit core: a variable CORE-VAR-001: a biomarker at a visit and a column are each written one way and returned in full (#8)
  • pass unit core: a variable CORE-VAR-001: a variable that was returned can be handed back, and cannot be changed (#8)
  • pass unit core: a variable CORE-VAR-001: the five value types are raw, baseline, change, fold change and percent change (#8)
CORE-VAR-002pass

A malformed variable is refused with a message that names what is wrong: not an object, neither or both of a biomarker and a column, an empty name, a value type that is not one of the five, a missing visit, a visit given with a baseline value, or a key that is not known.

  • pass unit core: a variable CORE-VAR-002: a malformed variable is refused with a message naming what is wrong (#8)
CORE-VAR-003pass

A variable that asks for a cut is no longer refused: it is returned with its cut, which the shared cut rule reads (CUT-SPEC-001).

  • pass unit core: a variable CORE-VAR-003: a variable that asks for a cut is no longer refused: it is returned with its cut, for the shared cut rule (#8, #43)
CORE-VAR-004pass

The value type raw is the participant's result for the biomarker at the visit, as the results table holds it.

  • pass unit core: value types on the synthetic study CORE-VAR-004: raw is the result as the table holds it at the visit (#8)
CORE-VAR-005pass

The value type baseline is the participant's result at the baseline visits named in settings. With several named, one result per visit is brought to one value by their mean, or by the statistic named in settings (min, max, first); with none named, the first visit in visit order is the baseline.

  • pass unit core: value types on the synthetic study CORE-VAR-005: baseline is the result at the baseline visit named in settings (#8)
  • pass unit core: value types on the synthetic study CORE-VAR-005: several baseline visits are brought to one value by their mean, or by the statistic named (#8)
  • pass unit core: value types on the synthetic study CORE-VAR-005: with no baseline visit named, the first visit in visit order is the baseline (#8)
CORE-VAR-006pass

The value type change is the result at the visit minus the baseline. A participant with no result at the visit, or no baseline result, has no change and is dropped and counted.

  • pass unit core: value types on the synthetic study CORE-VAR-006: a participant with no baseline result has no change, fold change or percent change, and is counted (#8)
  • pass unit core: value types on the synthetic study CORE-VAR-006: change is the result at the visit minus the baseline (#8)
CORE-VAR-007pass

The value type fold_change is the result at the visit divided by the baseline. A participant whose baseline is zero or negative has no fold change and is dropped and counted.

  • pass unit core: value types on the synthetic study CORE-VAR-007, CORE-VAR-008: a baseline of zero, or below it, gives no fold or percent change, and the participant is counted (#8)
  • pass unit core: value types on the synthetic study CORE-VAR-007: fold change is the result at the visit divided by the baseline (#8)
CORE-VAR-008pass

The value type percent_change is one hundred times the change divided by the baseline. A participant whose baseline is zero or negative has no percent change and is dropped and counted.

  • pass unit core: value types on the synthetic study CORE-VAR-007, CORE-VAR-008: a baseline of zero, or below it, gives no fold or percent change, and the participant is counted (#8)
  • pass unit core: value types on the synthetic study CORE-VAR-008: percent change is one hundred times the change divided by the baseline (#8)
CORE-VAR-009pass

label() names a variable in words, for an axis title or a legend: the column's name, or the biomarker, its visit and its value type.

  • pass unit core: a variable CORE-VAR-009: a variable is named in words for an axis or a legend (#8)
CORE-FRAME-001pass

frame() resolves named variables to one record per participant: the participant's id, under the name of the id column, and one field per variable, named as the caller named it. Participants are in the participant table's order when one is given, and otherwise in the order first seen in the results.

  • pass unit core: the frame on the synthetic study CORE-FRAME-001: the frame has one record per participant, holding the id and one field per variable, named as given (#8)
CORE-FRAME-002pass

On the synthetic study the frame for IL-6 change from Baseline to Week 4 has 186 participants and 14 dropped: 13 with no result at Week 4 and one whose result there is missing.

  • pass unit core: the frame on the synthetic study CORE-FRAME-002: IL-6 change from Baseline to Week 4 has 186 participants and 14 dropped (#8)
CORE-FRAME-003pass

A participant for whom a variable cannot be worked out is left out of the frame and counted, by reason and by variable. Every participant seen is in the frame or counted once: under the first variable, in the order given, that could not be worked out.

  • pass unit core: the frame on the synthetic study CORE-FRAME-003: every participant seen is either in the frame or counted once in the dropped list (#8)
CORE-FRAME-004pass

Only the results table is required. With it alone the frame resolves a biomarker variable and holds no participant column.

  • pass unit core: the frame on the synthetic study CORE-FRAME-004: the results table alone gives a frame, with no participant column in it (#8)
CORE-FRAME-005pass

A column variable is read from the participant table when that table is given and has the column, and otherwise from a column carried on the results rows.

  • pass unit core: the frame on the synthetic study CORE-FRAME-005: a column is read from the participant table when it is given, and otherwise from a column carried on the results rows (#8)
CORE-FRAME-006pass

A wide table with one row per participant needs no special handling: given as the results table, or as the participant table, each of its columns resolves as a column variable.

  • pass unit core: the frame on the synthetic study CORE-FRAME-006: a wide table with one row per participant resolves as it is, every column a variable (#8)
CORE-FRAME-007pass

Of several results for one participant, biomarker and visit, the first usable one in table order is used, and each later one is counted as an unused row.

  • pass unit core: what the frame leaves out CORE-FRAME-007: of several results for one participant, biomarker and visit the first usable one is used and the rest are counted (#8)
CORE-FRAME-008pass

A result that is missing or not a number is not a result: the row is counted as unused, and a participant with no other result at the visit is dropped and counted. Text that reads as a number is a number.

  • pass unit core: what the frame leaves out CORE-FRAME-008: a result that is missing or not a number is not a result, and a participant with no other is dropped and counted (#8)
CORE-FRAME-009pass

With a participant table given, it says who the participants are: a participant with results who is not in it is left out and counted, a participant in it with no result is dropped for a biomarker variable and counted, and a row with no id, or a second row for a participant, is counted as unused.

  • pass unit core: what the frame leaves out CORE-FRAME-009: participants in one table and not the other are each handled and counted (#8)
CORE-FRAME-010pass

A column read from the results rows must hold one value for the participant. A participant for whom it is empty, holds more than one value, or (for a column read as a number) is not a number is dropped and counted.

  • pass unit core: what the frame leaves out CORE-FRAME-010: a column carried on the results rows must hold one value for the participant; one that is empty, varies or is not a number is counted (#8)
CORE-FRAME-011pass

By default every variable is required. A variable not named in the required setting is left empty (null) in a participant's record instead of dropping the participant.

  • pass unit core: what the frame leaves out CORE-FRAME-011: a variable that is not required is left empty rather than dropping the participant (#8)
CORE-FRAME-012pass

Column names are settings, named as safety.viz names them, and their defaults are the synthetic study's: USUBJID, TEST, STRESN, VISIT, VISITNUM, with the participant table's id column the same as the results table's unless named.

  • pass unit core: settings CORE-FRAME-012: column names are settings, and their defaults are the synthetic study’s (#8)
CORE-FRAME-013pass

A call that cannot be made is refused with a message naming what is wrong: tables that are not arrays of records, a table that is not one of the two, variables not given by name, a name that is the id column's, a setting that is not known or has a value it cannot take, or a column a setting names that the table does not have.

  • pass unit core: settings CORE-FRAME-013: a call that cannot be made is refused with a message naming what is wrong (#8)
CORE-FRAME-014pass

The frame's records are plain text and finite numbers, and go to R through the connection as they are, the fields named as a statistics function takes them (strValueCol, strGroupCol).

  • pass unit core: what leaves the frame, and what the module is made of CORE-FRAME-014: the frame’s records go to R through the connection as they are, with the fields named as the statistics functions take them (#8)
CORE-FRAME-015pass

The frame changes nothing it is given: not the tables, the variables or the settings.

  • pass unit core: what leaves the frame, and what the module is made of CORE-FRAME-015: the frame changes nothing it is given (#8)
CORE-API-002pass

Both committed bundles export core (a page reads BioViz.core): variable, frame, label, the cut rule's cutPoints, cutGroup, cutLabels and cutWords, the rule for unscheduled visits' isUnscheduledVisit, scheduledResults and UNSCHEDULED_DEFAULTS, and the vocabulary VALUE_TYPES, CUTS, BASELINE_STATS, DEFAULT_SETTINGS, DROPPED and UNUSED.

  • pass unit core: what leaves the frame, and what the module is made of CORE-API-002: BioViz.core is exported by both committed bundles, with the variable, the frame and their vocabulary (#8)
CORE-BUILD-003pass

The core module imports nothing from outside src/core/, and reaches for no page, no chart and no network.

  • pass unit core: what leaves the frame, and what the module is made of CORE-BUILD-003: the core module imports nothing from outside src/core, and reaches for no page and no network (#8)
CORE-FRAME-016pass

visits() lists the visits of a results table in visit order: by the visit-order column when the table has one and otherwise by name with numbers counted as numbers, and only the visits with at least one usable result.

  • pass unit core: settings CORE-FRAME-016: the visits of a results table are listed in visit order, the ones with a usable result only (#9)
CORE-MAN-001pass

Both committed bundles export portfolio (a page reads BioViz.portfolio): the chart list, equal to src/data/portfolio.json, in safety.viz's portfolio manifest format, version 2.

  • pass unit the chart list CORE-MAN-001: BioViz.portfolio is the chart list, the same object in the source and in both committed bundles (#32)
CORE-MAN-002pass

The chart list validates against safety.viz's portfolio manifest schema at the recorded commit, and a list that breaks the format does not.

  • pass unit the chart list CORE-MAN-002: the chart list validates against safety.viz’s manifest schema at the recorded commit (#32)
CORE-MAN-003pass

The schema is safety.viz's src/data/schema/portfolio.json, copied byte for byte to src/data/schema/ by tools/vendor-portfolio-schema.mjs, with a record naming safety.viz's dev branch, the commit and the file's checksum and size; npm test fails when the file and its record disagree, and continuous integration compares the file with safety.viz at the recorded commit (npm run portfolio:check-source).

  • pass unit the chart list CORE-MAN-003: the copied schema matches its record, which names safety.viz’s dev branch and a commit on it (#32)
CORE-MAN-004pass

The chart list has one entry for each chart site/config.json marks available, and no other, keyed by its module, under its title and the name of the function the bundle exports for it; each entry names bio.viz as its library and the declared group biomarkers as its group, and takes the results table from the labs and vitals domain, required, and the participant table from the subject-level domain, optional.

  • pass unit the chart list CORE-MAN-004: every entry names bio.viz, is listed in the declared biomarker group, and takes the results table from labs and vitals and the participant table, optional, from the subject-level file (#32)
  • pass unit the chart list CORE-MAN-004: there is one entry for each available chart in site/config.json, under its title and its export, and no other (#32)
CORE-MAN-005pass

Each entry's settings are exactly its chart's column-name settings (the keys of its DEFAULT_SETTINGS ending in _col or carrying _col_), each with the chart's default and required exactly where the chart refuses null for it; a column setting of a table the entry does not name (the outcomes table of the biomarker screen, bio.viz#63) carries no column and is not required, whatever the chart's default, and the chart keeps that default when the setting is left out; participant_id_col, whose default null means id_col's name, reads id_col's standard column from the subject-level domain; and an unmapped setting is left out (unmappedSettings: "omit").

  • pass unit the chart list CORE-MAN-005: a chart that refuses a null column is passed nothing for an unmapped one (#32)
  • pass unit the chart list CORE-MAN-005: each entry’s settings are its chart’s column-name settings, with the chart’s defaults, required where the chart refuses no column; a setting of a table the entry does not name carries no column and is not required (#32, #99)
CORE-MAN-006pass

An export a module lists in api.data is documented under one heading of its own, and its fields are not held to the reference one by one; the core lists portfolio there.

  • pass unit API reference: held to the code CORE-MAN-006: an export listed as data is documented as one, under one heading, and its fields are not held one by one (#32)
CORE-MAN-007pass

The site publishes the chart list at portfolio.json, the same list a page that loads the bundle reads as BioViz.portfolio, and the format it names at schema/portfolio.json.

  • pass browser CORE-MAN-007: the site publishes the chart list as portfolio.json, the same list a page reads as BioViz.portfolio, and the format it names at schema/portfolio.json (#32)
CORE-MAN-008pass

Every column a setting of the chart list names, for every chart in it, is a column of the setting's domain in safety.viz's standard set, and a setting with no column is not required. The standard set is the domains of safety.viz's own manifest, read from the vendored safety.viz bundle and typed nowhere in this repository. A list that names an outcomes column against the results table, a column with no name, or a domain outside the set is refused by the same check.

  • pass unit the chart list CORE-MAN-008: every column a setting names, for every chart in the list, is a column of its domain in safety.viz’s standard set, read from the vendored safety.viz bundle; a list that names an outcomes column against the results table is refused (#99)
CORE-FRAME-017pass

Visit order is one total order, whatever order the rows come in: with a visit-order column, the visits that have a number first, by their least number, then the visits with no number; ties, unnumbered visits and a table with no order column by name, with numbers in a name counted as numbers.

  • pass unit core: settings CORE-FRAME-017: visit order is one total order, whatever order the rows come in: numbered visits by their least number, then visits with no number by name (#49)
CUT-SPEC-001pass

A biomarker variable, or a column read as a number, may carry a cut: median, tertiles, quartiles, or typed points in ascending order. variable() returns it with its cut, and label() says the cut after the variable: CRP at Baseline, cut at the median.

  • pass unit core: the cut rule CUT-SPEC-001: a biomarker or a number column may carry a cut: the median, the tertiles, the quartiles, or typed points in ascending order (#43)
CUT-SPEC-002pass

A malformed cut is refused with a sentence naming it: a name that is not one of the cuts, an empty list, a point that is not a finite number (named as it is: NaN, Infinity), points not each greater than the one before, typed points written alike to four significant digits, or a column cut that is not read as a number.

  • pass unit core: the cut rule CUT-SPEC-002: a malformed cut is refused with a sentence that names it (#43)
CUT-PTS-001pass

The cut points are R's quantile() default (type 7) on the values, one per participant, missing values left out, worked out the way R works them out, so each equals desktop R's to the last binary place; typed points are used as written.

  • pass unit core: the cut rule CUT-PTS-001: the cut points are R’s quantile(type = 7) on the values, missing ones left out, and typed points are used as written (#43)
CUT-PTS-002pass

A repeated cut point collapses, and the result says the points repeated; with no value there are no points and no groups.

  • pass unit core: the cut rule CUT-PTS-002: a repeated cut point collapses, and the result says the points repeated (#43)
CUT-GRP-001pass

Each participant is in the group R's cut(x, breaks = c(-Inf, points, Inf), right = TRUE) puts them in: a value equal to a cut point falls in the lower group, and a missing value is in no group.

  • pass unit core: the cut rule CUT-GRP-001: each participant is in the group R’s cut(right = TRUE) puts them in: a value equal to a cut point falls in the lower group, and a missing value in none (#43)
CUT-LBL-001pass

The groups are ordered low to high and labelled with their bounds (≤ a, > a, ≤ b, > z), each bound written to four significant digits as R's format(signif(p, 4), scientific = FALSE, trim = TRUE) writes it, a tie rounded to even.

  • pass unit core: the cut rule CUT-LBL-001: groups are ordered low to high and labelled with their bounds, each written to four significant digits as R’s signif() writes it (#43)
CUT-LBL-002pass

A bound however small or large is written in full with no trailing zero, as R writes it with scientific = FALSE: 0.000000000000000111, 0.0000001, 3382000000000000000000; no point a double holds is refused for its size.

  • pass unit core: the cut rule CUT-LBL-002: a bound however small or large is written in full with no trailing zero, as R’s format(scientific = FALSE) writes it (#43, #46)
CUT-GRP-002pass

Distinct points written alike make groups with the same label, and those groups are one, as R's cut() merges levels with the same label; the result says they merged.

  • pass unit core: the cut rule CUT-GRP-002: distinct points written alike make groups with the same label, which are one group, as R’s cut() merges levels with the same label, and the result says they merged (#43, #46)
CUT-STUDY-001pass

On the synthetic study, the core's frame gives the cut variable's values that desktop R reads, for the participants a filter keeps, and the points and groups made from them are R's.

  • pass unit core: the cut rule CUT-STUDY-001: on the synthetic study, the frame’s values of the cut variable, for the participants the filters keep, are R’s, and so are the points and the groups (#43)
CUT-DOC-001pass

The R recipe in the core's reference is, line for line, the one tools/r-cut.R runs to write the expected results.

  • pass unit core: the cut rule CUT-DOC-001: the R recipe in the core’s reference is, line for line, the one tools/r-cut.R runs to make the expected results (#43)
CORE-VISIT-001pass

isUnscheduledVisit() says whether a visit is unscheduled: when a list in unscheduled_visit_values names it, the list deciding alone and an empty list meaning no visit; and with no list, when its name matches unscheduled_visit_pattern, a regular expression written as /source/flags or as a plain source. With neither, no visit is unscheduled.

  • pass unit core: which visits are unscheduled CORE-VISIT-001: a visit is unscheduled when a list names it, and with no list when its name matches the pattern; a list decides alone, an empty one means no visit, and with neither no visit is unscheduled (#84)
CORE-VISIT-002pass

The rule's three settings, UNSCHEDULED_DEFAULTS, carry safety.viz's names and the defaults of its results over time chart, the default pattern equal to the one in the vendored safety.viz bundle; the copy's source names the safety.viz commit it was made from, which is the vendored one; and on every visit under every kind of setting the rule answers as safety.viz's own two functions do, read out of that bundle and run beside it.

  • pass unit core: which visits are unscheduled CORE-VISIT-002: the settings carry safety.viz’s names and the defaults of its results over time chart, and the rule answers as safety.viz’s own does, read from the vendored bundle (#84)
CORE-VISIT-003pass

scheduledResults() gives the rows of a results table at scheduled visits, in the table's order, with the names of the unscheduled visits found and how many rows were set aside. A row with no visit is kept, a table with no unscheduled visit comes back as it is, the visit column is the settings' own, and nothing given is changed.

  • pass unit core: which visits are unscheduled CORE-VISIT-003: `scheduledResults()` sets aside the rows at unscheduled visits and says which visits and how many rows; a table with none comes back as it is, and nothing given is changed (#84)
CORE-NEWS-001pass

The release log holds its shape: only the first section may be (Upcoming), a released section links nothing on the dev site, and the newest released section is the package version.

  • pass unit the release log CORE-NEWS-001: only the first section may be upcoming; a released section links nothing on the dev site; the newest released section is the package version (#56)
CORE-NEWS-002pass

A release's notes are short. The newest released section of the release log and the upcoming one are within the limits of obot.agent's release-notes skill: 600 words a section, 80 for the introduction, at most six bullets under "What's new" of at most 70 words each, 60 a bullet under "Also in this release", 100 a bullet under "Deprecated" or "Removed", 100 for "Tests and provenance", under those five headings in that order and no other, each bullet opening with its claim in bold. Words are counted as a reader meets them: a link counts as its text, and the issue and pull-request links that close a bullet are not counted. The released section opens on a "See it move" line that links its demo page and says what the release is.

  • pass unit the release log CORE-NEWS-002: the newest released section and the upcoming one are within the limits of a release’s notes, counted as a reader meets the words, under the five headings in their order; the released one opens on its demo page and says what the release is (#117)

Visual evidence

Every screenshot below is a committed baseline: the same picture is what the browser tests compare the page with and what is shown here. Click one for the picture at its full size.

Tests run with every module

40 tests of the site, the evidence pipeline and the repository’s own checks

These are recorded in every module’s evidence set. A requirement ID one of them carries belongs to another module’s page.

  • pass unit API reference: held to the code GC-SITE-004: a chart’s reference names every setting the chart has, and a setting it leaves out is a problem (#9)
  • pass unit evidence normalizer buildEvidenceSets splits records per module and duplicates shared scaffold records (#1)
  • pass unit evidence normalizer buildRun builds GitHub Actions run provenance from the environment (#1)
  • pass unit evidence normalizer compareEvidence flags status drift and test-set changes, ignoring screenshots (#1)
  • pass unit evidence normalizer compareEvidence ignores provenance so --check never drifts on generatedAt/environment/run (#1)
  • pass unit evidence normalizer moduleForFile routes test files to modules by path (#1)
  • pass unit evidence normalizer normalizePlaywright walks nested suites into browser-suite records (#1)
  • pass unit evidence normalizer normalizeVitest maps assertion results to unit-suite records (#1)
  • pass unit evidence normalizer parseTestName extracts requirement IDs and issue refs (#1)
  • pass unit evidence normalizer parseTestName recognizes any requirement-ID prefix, not just SH (#1)
  • pass unit evidence normalizer provenance lives in dedicated top-level keys; the records array stays timestamp-free (#1)
  • pass unit evidence page the page links the module’s requirement matrix and its committed evidence set (#7)
  • pass unit gallery the home page heads its word about the charts for one chart and for several (#26)
  • pass unit gallery the home page links each module’s evidence page and API reference, and the gallery (#7)
  • pass unit gallery the home page says there are no charts yet only while none is published (#9)
  • pass unit markdown: blocks a relative link points at the repository, and a link to another reference file at its page (#7)
  • pass unit markdown: inline keeps a code span inside a link label, and links a bare address in angle brackets (#7)
  • pass unit markdown: inline mdText strips the marks and keeps the words (#7)
  • pass unit markdown: inline reads nothing inside a code span as a link or as emphasis (#7)
  • pass unit markdown: inline renders code, links, bold and italic, and escapes everything else (#7)
  • pass unit R check page RCON-PAGE-001: the page has a button that starts R, the stated tolerance and the versions desktop R used (#3)
  • pass unit R check page RCON-PAGE-002: the recorded megabytes, requests and seconds are shown for cold, reload and warm, with how they were measured (#3)
  • pass unit R check page RCON-PAGE-003: with no recorded measurement the page says so and prints no number in its place (#3)
  • pass unit repo hygiene no source or test file carries a machine-specific absolute path (#1)
  • pass unit requirements-lib: freshness guard flags added and removed requirement IDs (#1)
  • pass unit requirements-lib: freshness guard flags changed requirement text (#1)
  • pass unit requirements-lib: freshness guard reports fresh when the committed set matches a fresh extraction (#1)
  • pass unit requirements-lib: matrix parsing ignores the header, separator, and non-requirement content (#1)
  • pass unit requirements-lib: matrix parsing keeps an escaped pipe inside a requirement cell as a single row (#1)
  • pass unit requirements-lib: matrix parsing maps each requirement ID to its reviewed text (#1)
  • pass unit requirements-lib: requirement set wraps the parsed map with module + matrix provenance (#1)
  • pass unit requirements-lib: unregistered matrices passes when every matrix file is registered, ignoring the README and non-markdown files (#1)
  • pass unit requirements-lib: unregistered matrices reports a matrix file no module in site/config.json names (#1)
  • pass unit site pages escapeHtml escapes the five HTML-significant characters (#1)
  • pass unit site pages renderShell fills title, description, version and root, and leaves no token behind (#1)
  • pass unit site pages summarizeModule counts requirement rows and passing test records (#1)
  • pass unit site pages the home page links to the R check page (#3)
  • pass unit site pages the home page lists each registered module with its counts and a link to its matrix (#1)
  • pass unit site validation: internal links flags internal links and asset references that do not resolve (#1)
  • pass unit site validation: internal links passes a site whose internal links all resolve, ignoring external and fragment links (#1)

Checking this page

npm ci
npm run evidence:check   # rerun every test and compare with the committed evidence set
npm run evidence         # rebuild docs/evidence/core/evidence.json