Skip to content
This repository was archived by the owner on Jul 10, 2026. It is now read-only.
Closed
Changes from 1 commit
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -52,6 +52,6 @@
from: alice,
})
).result,
).toBe(1n);
).toBe(999n);

Check failure on line 55 in src/ts/counter.test.ts

View workflow job for this annotation

GitHub Actions / checks / JS Tests

src/ts/counter.test.ts > Counter Contract > e2e

AssertionError: expected 1n to be 999n // Object.is equality - Expected + Received - 999n + 1n ❯ src/ts/counter.test.ts:55:7

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

});
});
Loading