Repository navigation
Say under each SQA element's link what the link should be - #95
Merged
Merged
Conversation
The SQA Elements dialog takes a link for each element, and nothing said what to link: for "Test plan", the pipeline, the tests or a document; for the four elements about dependencies, which of the build file, the lock file and the README. The SQAP now gives each element of a product a line of evidence, what its record links to (acc/iac/docs/sqap!24). SIM loads that line with the elements, from SQAP revision draft 0e98a07 after 1.0.0, into a new SQA_ELEMENT.EVIDENCE column, and the dialog shows it under the link, such as "The lock file; where the build tool has none, the build file or README that gives exact versions". It runs on under the note, so that it takes a line or two, not three. The two elements SIM sets itself take no link and show no line. The loader refuses an elements.json without the lines. The revision changes nothing else of the elements, so their section links and the user guide's four links to section 4.3 move to it, and container/oracle/upgrade/2.12.0_sqa_element_evidence.sql adds the column and the lines to an existing database. Co-Authored-By: Claude Fable 5.2 <[email protected]>
slominskir
approved these changes
Nov 18, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The SQA Elements dialog takes a link for each element, and nothing said what to link. Under each link there is now a line from the SQAP that says what it should be, such as "The lock file; where the build tool has none, the build file or README that gives exact versions".
evidence(acc/iac/docs/sqap!24). SIM loads it with the elements into a newSQA_ELEMENT.EVIDENCEcolumn, from SQAP revision draft0e98a07after 1.0.0.container/oracle/sqa_elements_sql.pyrefuses anelements.jsonwithout the lines.Release notes
Under each link in the SQA Elements dialog, SIM now says what the SQAP expects the link to be.
Upgrade. On an existing database, as
SIM_OWNER, after2.11.1_sqap_dependencies_merged.sql:container/oracle/upgrade/2.12.0_sqa_element_evidence.sql: addsSQA_ELEMENT.EVIDENCE, fills it for the 16 elements, moves their section links and revision to0e98a07, and makes the columnNOT NULL.It must run after the 2.11.1 script, which removes the retired element that has no evidence. The script is named for 2.12.0, since this is a feature: rename it if it ships in another version.
Checks
./gradlew build: passes.uv run --locked zensical build --strict: no issues../gradlew integrationTestagainst a new stack built from this branch (on ports of its own, since another stack held the defaults): 93 tests, 0 failed, before and after the last style change. The newPagesIT.elementsSayWhatTheirLinkPointsTochecks that every row has a line in the Link column, the text of one, and the footer.19bcfbawith the 2.11.1 script's updates, then ran the new script: 16 rows updated, each identical to a new database's, and the columnNOT NULL.tbrown, 1400 px wide): added a product, rated it Full, and opened its SQA Elements dialog. All 14 recordable elements show their line under the link, on one or two lines; the two SIM sets show none; no console errors.docker compose logs sim: the only errors come from the tests' rejection cases.Decisions
Prepared-by: Anthropic Claude Code:claude-fable-5-2
🤖 Generated with Claude Code