Add `insane_zero_fee_channel_open` test to exported tests
What the developer wrote
Authored by Carla Kirk-Cohen
Add `insane_zero_fee_channel_open` test to exported tests
What changed, and why it matters
This commit changes a single Rust test annotation so that an existing test named `test_insane_zero_fee_channel_open` is included in the project's exported/external test suite. It does not modify production code, protocol logic, or any behavior visible to users or network peers. There is no security-relevant change.
No action required. This is a non-security test-suite maintenance commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff replaces #[test] with #[xtest(feature = "_externalize_tests")] on fn test_insane_zero_fee_channel_open in lightning/src/ln/channel_open_tests.rs. This is purely a test-suite bookkeeping change: it exposes an existing internal test to the externally-runnable test collection. No implementation code, validation rules, fee checks, or channel-open logic are altered.
Changed components
lightning/src/ln/channel_open_tests.rsInspect captured patch +1 / −1
diff --git a/lightning/src/ln/channel_open_tests.rs b/lightning/src/ln/channel_open_tests.rs
index 72d9cca..3fd546a 100644
--- a/lightning/src/ln/channel_open_tests.rs
+++ b/lightning/src/ln/channel_open_tests.rs
@@ -622,7 +622,7 @@ pub fn test_insane_channel_opens() {
});
}
-#[test]
+#[xtest(feature = "_externalize_tests")]
fn test_insane_zero_fee_channel_open() {
let mut cfg = UserConfig::default();
cfg.manually_accept_inbound_channels = true;
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.