Add python integration test for spontaneous keysend payments#923
Conversation
|
👋 I see @tnull was un-assigned. |
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
tnull
left a comment
There was a problem hiding this comment.
CI is currently not available, so we'll need to wait a bit. One comment for now
0a308cb to
8056689
Compare
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
8056689 to
3c9be11
Compare
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
|
🔔 2nd Reminder Hey @tnull! This PR has been waiting for your review. |
tnull
left a comment
There was a problem hiding this comment.
This needs a rebase now, sorry!
|
@tnull fine, the conflit is resolved and i notice the CI is back ! |
tnull
left a comment
There was a problem hiding this comment.
Please cleanup the commit history. It should just be two commits: first the prefactor extracting logic into the helper, then using the helper adding the new test case.
Please also make sure to follow the guidance on https://cbea.ms/git-commit/ for how to format/structure commit messages.
Duplicated node setup, funding, channel opening, and teardown logic made integration tests harder to read and maintain. Hard-coded ports also risked collisions when tests run in parallel. Introduce reusable helpers for two-node setup, funding, channel ready waiting, and cleanup. Bind ephemeral ports to avoid conflicts, and refactor test_channel_full_cycle to use them without changing test behavior.
Exercise the spontaneous payment (keysend) path through the Python UniFFI bindings after a channel is ready. Assert events, custom TLV records, and persisted payment metadata on both sender and receiver.
51df0ce to
b318ccd
Compare
sure. history cleaned @tnull |
Hello @tnull x @enigbe x @Camillarhi This commit adds the test_spontaneous_payment method which :
Motivation
The python bindings has not coverage for
send_with_custom_tlvsRun the new test