Skip to content

Jenner compatibility tests for 3 script(s)#3

Open
lwsinclair wants to merge 1 commit into
dominodatalab:mainfrom
lwsinclair:jenner-check/initial-bundles
Open

Jenner compatibility tests for 3 script(s)#3
lwsinclair wants to merge 1 commit into
dominodatalab:mainfrom
lwsinclair:jenner-check/initial-bundles

Conversation

@lwsinclair

Copy link
Copy Markdown

Jenneranalytics.com provides an API that runs SAS code, with support for more than 200 SAS procedures. You can also use it with Anthropic Claude Code AI in a collaborative workspace. It's available for Mac on the Apple App Store, and by license for Windows and Linux. Your SDTM converters here run on it unmodified — this PR adds a few compatibility bundles so you can see for yourself.

Yes, AI was used to develop this PR as is most code in modern businesses today.

We support the larger community by

(1) increasing access to SAS-compatible systems,
(2) by providing test coverage and a test coverage framework to public SAS repos in order to encourage the use of best practices in software engineering.

This PR is our way of giving back to the developers whose code we use to validate the SAS-compatible Jenner system. We test against all SAS code in the world to validate our compatibility. These tests are the way we build our product. But we do not want to just keep them for ourselves: we share some of those tests with the repo owner so that they benefit from the automated test coverage as well.

Everything lands under a single new jenner-check/ folder, so nothing else in the repo moves:

jenner-check/
├── t001_dm_xpt_to_sdtm/   # from prod/sdtm/dm.sas — Demographics
├── t002_vs_xpt_to_sdtm/   # from prod/sdtm/vs.sas — Vital Signs (+ a PROC MEANS summary)
├── t003_ts_xpt_to_sdtm/   # from prod/sdtm/ts.sas — Trial Summary
└── run_jenner.sh / .bat / .sas + README.md

Each bundle pairs one of your SDTM converters with a small XPORT sample (a handful of CDISC Pilot01-style rows per domain) and a frozen snapshot of the run, so the xport read and the copy into SDTMBLND/SDTMUNBD run end to end in isolation. Run them all with cd jenner-check && ./run_jenner.sh --all, or POST any script.sas straight to the API or open the hosted workspace at jenneranalytics.com.

One thing I liked: the way domino.sas centralizes the whole environment — resolving SDTMBLND/SDTMUNBD and the rest from environment variables and wiring up SASAUTOS — keeps every domain program down to the essential xport read plus the copy, and the domain-per-file naming makes the converter set very easy to read. Tidy SCE setup.

No response needed — merge, cherry-pick a folder, or close as you like. To opt out of any future PRs like this, just say no-more-prs in a comment or open an issue titled jenner-check: opt out.


Lawrence W. Sinclair
CEO / Jenner Analytics Ltd
jenneranalytics.com
linkedin.com/in/lwsinclair/

Adds a self-contained jenner-check/ folder with compatibility bundles built
from the repo's SDTM converters (prod/sdtm/dm.sas, vs.sas, ts.sas). Each
bundle writes a small CDISC Pilot01-style sample to a SAS XPORT (v5)
transport file and imports it via libname xport into SDTMBLND/SDTMUNBD,
mirroring the production converters, with a frozen expected result and a
readable snapshot of the run. Includes the run_jenner runner (sh/bat/sas)
and a README. All three bundles pass against the live Jenner API.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant