Skip to content

fix: repair JMeter withdraw race setup and payment pagination - #920

Closed
motorina0 wants to merge 1 commit into
combine/alanbits-extension-releasesfrom
fix/jmeter-withdraw-race
Closed

motorina0 wants to merge 1 commit into
combine/alanbits-extension-releasesfrom
fix/jmeter-withdraw-race

Conversation

@motorina0

Copy link
Copy Markdown
Collaborator

The withdraw race plan exports withdrawLinkRes during setup but imports withdrawLinkCallback in its workers, leaving an unresolved variable in all 100 JSON requests. Import the exported response, define the missing mirror port, use the configured server URL in the page assertion, and request all attempted payments instead of the API's default page of 10.

Validation against LNbits fix_pydantic2_changes at 57b88dfdc with FakeWallet and JMeter 5.6.3:

  • The unchanged mandatory 001_extensions-enable-all.jmx passed for all 56 included extensions (298 top-level JTL records, zero failures).
  • The repaired race plan sends 100 valid requests, all returning HTTP 201, and retrieves all 100 payments.
  • The race suite still fails its unchanged final assertion: one withdrawal succeeds, while the test requires exactly two. Reproduced on both test instances; leaving this PR as a draft because the suite is not fully green.
  • XML parsing and git diff --check pass.

Only the existing race plan is changed; no new scenarios are added.

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