Write unit tests for EVM order service

[chibie]

User Story

As a developer, I want to write tests for the OrderService functions so that the core order management logic is thoroughly tested.

Acceptance Criteria

1. GIVEN the CreateOrder method
   WHEN testing
   THEN validate it handles fetching order data, initializing user operation, creating calldata, sponsoring, signing, sending, and updating order status

2. GIVEN the RefundOrder method
   WHEN testing
   THEN validate it handles fetching lock order data, initializing user operation, creating calldata, sponsoring, signing, sending, and updating order status

3. GIVEN the RevertOrder method
   WHEN testing
   THEN validate it handles fetching order data, calculating revert amount, initializing user operation, creating calldata, sponsoring, signing, sending, and updating order

4. GIVEN the SettleOrder method
   WHEN testing
   THEN validate it handles fetching lock order data, initializing user operation, creating calldata, sponsoring, signing, sending, and updating order

Product & Design Links

Tech Details

• Mock out RPC client calls to the bundler and paymaster APIs

Open Questions

Notes/Assumptions

[xlassix]

After carefully looking through the services and the nested loop of API call from

• getNonce
• GetPaymasterAccount
• executeBatchTransferCallData
• executeBatchCreateOrderCallData
• eth_getUserOperationReceipt
• pm_accounts

all has to be mocked with fuzzy reponses, unlike the userop_test for user_op which the RPC values returned are not been consumed. here in evm.go. "Everything is in use" and dependant on the next

[Supa-mega]

Can I take care of this issue?

[viktrified]

Can I jump on this task?