Skip to content

Conversation

@ARR4N
Copy link
Collaborator

@ARR4N ARR4N commented Jan 2, 2026

Why this should be merged

We weren't running execution spec tests for over a year because they are silently skipped if not present. They're introduced in #252 but it's not possible to guarantee that they're actually being run.

How this works

Introduces a flag to ./tests, which will cause a lack of spec-test directories or ./tests submodules to be fatal instead of silently skipped.

How this was tested

Repeated CI runs on contiguous commits, the latter only adding the missing tests:

  1. With flag set but no tests present, demonstrates expected failure.
  2. After merging main with introduction of tests, no longer fails.

@ARR4N ARR4N changed the title feat: flag to fail instead of skip if execution spec tests unavailable feat: flag to fail instead of skip if ./tests cases are missing Jan 2, 2026
@ARR4N ARR4N marked this pull request as ready for review January 2, 2026 12:27
@ARR4N ARR4N requested a review from ceyonur January 2, 2026 12:27
@ARR4N ARR4N enabled auto-merge (squash) January 2, 2026 12:40
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.

2 participants