Skip to content
This repository was archived by the owner on Jul 10, 2026. It is now read-only.

test: flip assertion to make the test fail #131

Closed
xorsal wants to merge 4 commits into from
Closed

test: flip assertion to make the test fail #131

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d05889d
test: flip assertion to make the test fail
xorsal May 25, 2026
fc07f23
chore: retrigger CI for canary validation
alice-aztec[bot] May 26, 2026
ca9d182
chore: trigger CI
xorsal May 26, 2026
9e40520
chore: trigger CI
xorsal May 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/ts/counter.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,6 @@ describe("Counter Contract", () => {
from: alice,
})
).result,
).toBe(1n);
).toBe(999n);

@qodo-code-review qodo-code-review Bot May 25, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Failing counter expectation 🐞 Bug ≡ Correctness

src/ts/counter.test.ts now asserts the counter equals 999n after a single increment(), but the
contract increments by exactly 1, so the test will always fail and block CI/merges.
Agent Prompt 
## Issue description
The `Counter Contract` e2e test expects the counter to be `999n` after one increment, but the contract increments the stored value by `+1`. This makes the test deterministically fail.

## Issue Context
The Noir contract implementation and its Noir unit tests both indicate that calling `increment()` once results in the counter value `1`.

## Fix Focus Areas
- src/ts/counter.test.ts[44-56]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

});
});