midnight-cq:wallet-testing

To test Effect and Either abstractions in Vitest, you unwrap the results to assert success and failure paths directly within async and pure capabilities. This approach validates returned values and error handling logic for custom wallet implementations.

Asserting RxJS observable state in WalletBuilder tests requires first-value and multi-emission strategies to prevent race conditions. You verify state transitions while ensuring proper cleanup of subscriptions per test to avoid memory leaks.

Creating test doubles for async services involves building complete capability and service doubles using Layer-based service provisioning. This setup allows you to mock proving and submission services for unit and integration testing of wallet variants.

Yes, you can use Vitest to test branded type fixtures within a custom WalletBuilder composition. The testing process includes constructing branded type fixtures and wiring them with test doubles to validate your wallet variant's specific capabilities.

Wallet SDK observable tests leak memory or behave flaky when subscriptions are not properly cleaned up per test. Using structured first-value and multi-emission strategies prevents races and ensures stable observable state testing.