test(frontend): fix stale Claim-all confirm assertion in placements panel (#253) #736
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!736
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "qa/253-claim-all-panel-test-stale"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Test-only fix for a red test on main, found while verifying #253.
LimitOrderMyPlacementsPanel.test.tsxasserted the exact Claim-all confirm string, but #259 (2e6f2cf) added a gas-estimate suffix to that copy ("... Est. ~X LUNC gas (saves ~Y LUNC vs N separate claims).") without updating this panel test — so it has failed since that merge:The feature is fine; this is a stale assertion. Match the stable confirm prefix via
expect.stringContaining(...). The exact gas copy is already asserted by regex inlimitExpiredClaimBatch.test.ts, so the panel test stays decoupled from volatile gas numbers with no coverage loss.npx vitest runon the three #253 files (useLimitExpiredClaimMutation,limitExpiredClaimBatch,LimitOrderMyPlacementsPanel) -> 13/13.Relates to #253 / #259. Not a close — the #253 browser Claim-all sign-off is still pending.
mentioned in issue #253
mentioned in issue #259
mentioned in commit
487f46569a