frostney / frostney/GocciaScript
Migrate test discovery onto lwpt test
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Summary
Run the *.Test.pas suite via lwpt test discovery.
Why
Consolidating test discovery and execution onto lwpt test completes the toolchain migration for the Pascal unit suite.
Current behavior
Pascal unit tests run via the project's own build/runner.
Expected behavior
lwpt testdiscovers, compiles, and runs the*.Test.passuite at parity.
Scope notes
- Part of the lwpt migration (parent #826).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing Pascal unit test build/runner and the lwpt test discovery entry point, using the *.Test.pas pattern and parent issue #826 for migration context. Confirm which tests are currently discovered and how they are compiled and run. Done means lwpt test discovers, compiles, and runs the full suite at parity with the current behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100