Skip to content

fix: classify TunnelMeOut as an admin extension in JMeter - #925

Merged
motorina0 merged 1 commit into
mainfrom
fix/jmeter-tunnel-admin
Oct 30, 2026
Merged

motorina0 merged 1 commit into
mainfrom
fix/jmeter-tunnel-admin

Conversation

@motorina0

@motorina0 motorina0 commented Oct 30, 2026 •

Copy link
Copy Markdown
Collaborator

001_extensions-enable-all.jmx visits enabled extensions as a regular user. TunnelMeOut restricts its page to the superuser and correctly returns HTTP 403, but the test expected HTTP 200 because TunnelMeOut was missing from adminExtensions.

Add tunnel_me_out to the existing list alongside nostrclient, so the existing admin-extension assertion handles it.

Validation:

  • XML parsing and git diff --check passed.
  • The full 001 run passed installation, enable/disable, and uninstallation for all 57 extensions. Both enabled-page checks for TunnelMeOut returned HTTP 403 and passed the existing admin assertion.
  • The run later stopped during SMTP reinstallation after fetching the GitHub registry manifest failed (Release not found). A second run hit the same manifest-fetch failure while installing Nostr Bunker. Neither run completed successfully; these failures were separate from the TunnelMeOut assertion.
  • CI is pending.

@motorina0
motorina0 merged commit e5adbfa into main Oct 30, 2026
3 checks passed
@motorina0
motorina0 deleted the fix/jmeter-tunnel-admin branch October 30, 2026 17:51
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.

1 participant