Refactor for Phasal Test Execution#28
Conversation
Refactors the test runner to treat setup, main, and teardown as three distinct, sequential phases. - Teardown tests now always run, even if main tests fail. - Focusing on a main test no longer prevents setup and teardown tests from running. - If a setup test fails, main and teardown tests are skipped.
|
👋 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 For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This submission refactors the test runner to execute tests in three distinct phases: setup, main, and teardown. This ensures that teardown tests always run, even if main tests fail, and that focusing on a main test does not prevent setup and teardown tests from running.
PR created automatically by Jules for task 2882670780084999242 started by @justiceo