Skip to content

fix(test): use canonical extension name in setup submit test - #2158

Merged
henrypark133 merged 1 commit into
stagingfrom
fix/extensions-setup-test-canonical-name
Apr 8, 2026
Merged

henrypark133 merged 1 commit into
stagingfrom
fix/extensions-setup-test-canonical-name

Conversation

@henrypark133

Copy link
Copy Markdown
Collaborator

Summary

  • Fix failing test_extensions_setup_submit_returns_failure_when_not_activated by using an underscored channel name (test_failing_channel) instead of hyphenated (test-failing-channel)
  • canonicalize_extension_name() converts hyphens to underscores, so configure() was looking for test_failing_channel.capabilities.json which didn't exist, causing an early Err before reaching the activation path the test exercises

Test plan

  • cargo test --lib channels::web::server::tests::test_extensions_setup_submit_returns_failure_when_not_activated passes

🤖 Generated with Claude Code

The test used a hyphenated channel name ("test-failing-channel") but
canonicalize_extension_name() converts hyphens to underscores. This
caused configure() to look for "test_failing_channel.capabilities.json"
which didn't exist, returning an early Err before reaching the
activation code path the test was designed to exercise.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings April 8, 2026 16:57
@github-actions github-actions Bot added scope: channel/web Web gateway channel size: XS < 10 changed lines (excluding docs) risk: medium Business logic, config, or moderate-risk modules contributor: core 20+ merged PRs labels Apr 8, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR fixes a failing web channel setup submission test by aligning the test channel name with the extension-name canonicalization rules used by the runtime (hyphens are converted to underscores), ensuring the test reaches the intended activation-failure path.

Changes:

  • Update the test channel name from a hyphenated form to an underscored form so the generated *.capabilities.json filename matches what configure() looks for.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates a test case in src/channels/web/server.rs by renaming a channel variable to use an underscore instead of a hyphen. I have no further feedback to provide.

@henrypark133
henrypark133 merged commit 1eaea59 into staging Apr 8, 2026
23 checks passed
@henrypark133
henrypark133 deleted the fix/extensions-setup-test-canonical-name branch April 8, 2026 21:34
@claude

claude Bot commented Apr 8, 2026

Copy link
Copy Markdown

Code review

No issues found.

@ironclaw-ci ironclaw-ci Bot mentioned this pull request Apr 10, 2026
@ironclaw-ci ironclaw-ci Bot mentioned this pull request Apr 18, 2026
theredspoon pushed a commit to theredspoon/ironclaw that referenced this pull request Jun 21, 2026
…2158)

The test used a hyphenated channel name ("test-failing-channel") but
canonicalize_extension_name() converts hyphens to underscores. This
caused configure() to look for "test_failing_channel.capabilities.json"
which didn't exist, returning an early Err before reaching the
activation code path the test was designed to exercise.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contributor: core 20+ merged PRs risk: medium Business logic, config, or moderate-risk modules scope: channel/web Web gateway channel size: XS < 10 changed lines (excluding docs)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants