Skip to content

Add regression test for protocol fee bps read after multiple sequential updates #365

@Chucks1093

Description

@Chucks1093

Summary
The protocol fee bps read is tested after a single update, but not after multiple sequential updates. A regression test that performs three fee config updates and reads the bps after each confirms the stored value always reflects the most recent update.

Scope

  • add a regression test that updates the protocol fee bps three times with distinct values
  • read the fee bps after each update and assert it matches the most recent value
  • assert the earlier values are not returned after being overwritten

Acceptance Criteria

  • the fee bps read returns the latest value after each update
  • earlier values are not returned after being overwritten
  • the test covers at least three sequential updates

Contributor coordination: if you pick this up, reach out in Telegram for updates or clarification: https://t.me/accesslayerorg

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveIssues in the Stellar wave program

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions