Priority order
Order: 03 of 09
Priority: P1 prerequisite for Oracle stories
Problem
Before any Oracle-specific bug or SQL change is implemented, we need to know whether this project can run Oracle integration tests locally through Docker and in GitHub Actions.
Scope
- Find a valid Oracle database image usable from Docker for local development.
- Determine whether the same or an equivalent image can run reliably in GitHub Actions.
- Update or add Docker/GitHub Actions setup as needed to run Oracle tests.
- Enable Oracle test execution only after the environment is reproducible.
Mandatory test-first workflow
- Create or enable tests first to prove the current Oracle behavior can be exercised.
- Do not implement Oracle production-code fixes until Oracle tests can run locally or in CI.
- If Oracle tests cannot run, document the blocker and proposed alternative before touching Oracle production code.
Acceptance criteria
- Document the selected Oracle image and any licensing/availability constraints.
- Oracle integration tests can be run with clear local instructions, or the blocker is documented.
- GitHub Actions feasibility is documented and, if feasible, wired into CI.
- This issue is completed before any Oracle-specific story is implemented.
Source: docs/Project-Analysis-Issue-Drafts.md.
Priority order
Order: 03 of 09
Priority: P1 prerequisite for Oracle stories
Problem
Before any Oracle-specific bug or SQL change is implemented, we need to know whether this project can run Oracle integration tests locally through Docker and in GitHub Actions.
Scope
Mandatory test-first workflow
Acceptance criteria
Source:
docs/Project-Analysis-Issue-Drafts.md.