Skip to content

fix: cheatcode test read incorrectly from note #12710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LHerskind merged 1 commit into from
Mar 13, 2025
Merged

fix: cheatcode test read incorrectly from note #12710

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 5 additions & 1 deletion yarn-project/end-to-end/src/e2e_cheat_codes.test.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,11 @@ describe('e2e_cheat_codes', () => {

// check if note was added to pending shield:
const notes = await cc.aztec.loadPrivate(admin, token.address, balancesAdminSlot);
const values = notes.map(note => note.items[0]);

// @note If you get pain for dinner, this guys is the reason.
// Assuming that it is still testing the token contract, you need to look at the balances,
// and then the type of note, currently a `UintNote` which stores fields: [owner, randomness, amount]
const values = notes.map(note => note.items[2]);
const balance = values.reduce((sum, current) => sum + current.toBigInt(), 0n);
expect(balance).toEqual(mintAmount);
// docs:end:load_private_cheatcode
Expand Down