Skip to content

Conversation

@guerler
Copy link
Contributor

@guerler guerler commented Feb 3, 2026

Adds minor additional tests to increase test coverage for newly highlighted release features.

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

class TestWorkflowCompletionManagerHookTracking:
"""Tests for WorkflowCompletionManager hook execution tracking."""

def test_mark_hook_executed_records_hook_name(self):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a big fan of making sure the key points in the interface are tested, not every small detail. I am almost certain I deleted those tests from claude.

Also note that the hook execution itself is covered in selenium.

@@ -0,0 +1,37 @@
import { describe, expect, it } from "vitest";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these are nice, thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants