MSSQL spike: check whether extension tests run in CI #312

New issue

Closed

opened 2026-11-10 08:17:30 +00:00 by david · 1 comment

david commented

2026-11-10 08:17:30 +00:00

Owner

Summary

Find out whether the postgres extension tests run in CI, so the mssql tests are not assumed to run when they won't.

Background

The new mssql extension mirrors extensions/postgres/. The root package.json test script today lists specific test paths and does not include the postgres tests. This step only records the facts; it adds no code. Stage 2 later adds the mssql tests to the root test script, and this answer shapes that work.

Depends on: #311

Implementation Details

Read the root package.json test script and list which test files it runs. Note whether extensions/postgres/*.test.* is included.
Inspect the CI workflow files (.forgejo/workflows/, .github/workflows/) and note which command runs tests.
If Forgejo Actions is available (Forgejo v16+), use forgejo_action_runs to see a recent run and confirm what executed.
Append a "CI test coverage" section to extensions/mssql/spike/dependency-check.md (create the file/directory if the first step has not landed yet) stating: are postgres tests in the test script, does CI run npm test, and what the mssql tests must do to be picked up.

Acceptance Criteria

extensions/mssql/spike/dependency-check.md has a "CI test coverage" section.
It states whether postgres tests are in the root test script.
It states which command CI runs (or that no CI runs tests).
It states what Stage 2 must do so mssql tests run in CI.
No code changes.

Test Plan

Read the section and verify each claim against package.json and the workflow files named in it.

## Summary Find out whether the postgres extension tests run in CI, so the mssql tests are not assumed to run when they won't. ## Background The new mssql extension mirrors `extensions/postgres/`. The root `package.json` `test` script today lists specific test paths and does not include the postgres tests. This step only records the facts; it adds no code. Stage 2 later adds the mssql tests to the root `test` script, and this answer shapes that work. **Depends on:** #311 ## Implementation Details 1. Read the root `package.json` `test` script and list which test files it runs. Note whether `extensions/postgres/*.test.*` is included. 2. Inspect the CI workflow files (`.forgejo/workflows/`, `.github/workflows/`) and note which command runs tests. 3. If Forgejo Actions is available (Forgejo v16+), use `forgejo_action_runs` to see a recent run and confirm what executed. 4. Append a "CI test coverage" section to `extensions/mssql/spike/dependency-check.md` (create the file/directory if the first step has not landed yet) stating: are postgres tests in the `test` script, does CI run `npm test`, and what the mssql tests must do to be picked up. ## Acceptance Criteria - [ ] `extensions/mssql/spike/dependency-check.md` has a "CI test coverage" section. - [ ] It states whether postgres tests are in the root `test` script. - [ ] It states which command CI runs (or that no CI runs tests). - [ ] It states what Stage 2 must do so mssql tests run in CI. - [ ] No code changes. ## Test Plan Read the section and verify each claim against `package.json` and the workflow files named in it.

david added this to the MSSQL: M1 - Dependency checks milestone

2026-11-10 08:17:30 +00:00

david added the

chore

label

2026-11-10 08:17:30 +00:00

david referenced this issue

2026-11-10 08:17:52 +00:00

MSSQL spike: scaffold spike directory and must-reject corpus #313

david referenced this issue

2026-11-10 08:39:01 +00:00

312: MSSQL spike: check whether extension tests run in CI #333