Add support for non-default tests #48
Conversation
Tests can now be marked with `default = false` in `limmat.toml`. These tests are excluded from the default execution set (when no `--tests` argument is provided) but can be explicitly included by specifying them with `--tests`. If a default test depends on a non-default test that is not included, the configuration will fail to parse, preventing unexpected failures or implicit inclusion. - Added `default` field to `Test` struct in `src/config.rs`. - Updated `Config::parse_tests` filtering logic. - Updated `limmat.schema.json`. - Added unit tests for filtering logic and dependency constraints.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
Add support for non-default tests in configuration.
This allows defining tests that are expensive or specialized and shouldn't run on every invocation, but can be manually triggered.
Tests marked
default = falseare skipped unless explicitly matched by--tests. Dependencies are strict: if an included test depends on an excluded non-default test, the configuration will fail.PR created automatically by Jules for task 2530185326329134781 started by @bjackman