-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
add tests for transaction-planner #690
add tests for transaction-planner #690
Conversation
const mockPlanTransaction = vi.hoisted(() => vi.fn()); | ||
vi.mock('@penumbra-zone/wasm', () => ({ | ||
planTransaction: mockPlanTransaction, | ||
})); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We didn't get rid of the indexed-db global in wasm and we don't have that goal anymore, so we have no choice but to use mock here
web/packages/wasm/crate/tests/build.rs Lines 413 to 420 in 1edd2af
Actually wasm planner is tested with one case in rust tests, I think in future we need to write more rust tests for wasm planner |
Agree, tests in the crate will be far more meaningful. Could you create a tracking issue with a proposal of tests we can write for the crate to increase coverage on that side? |
Yep #691 |
The simplification of wasm transaction planner #609 is already finished, so it no longer makes sense for us to hold off on these tests