We need to prepare detailed test case specification that we will retest every week (smoke tests).

Save it to docs/test-cases.md

Test cases should cover all implemented user stories from docs/user-stories.md . Only include SPV mode, no RPC mode testing at this point.

Prerequisites

We need a shared prerequisites document that will be a precondition of all scenarios. In this document, describe how to configure dash-evo-tool for testing in SPV mode on testnet. I think crafting .env file is best approach there.

Tests should be execute on testnet. Assume you have a wallet seed with some tDASH. Use it as a "bank", don't create any objects there. Ensure as many tDASH as possible are moved back to a core address with index 0 of the "bank" wallet. See https://github.com/dashpay/dash-evo-tool/blob/bc3cf0bc3145cbf60152a441a4518bf3fe7481e3/tests/backend-e2e/README.md to better understand the "bank" concept, but you don't have to follow it closely.

Test case structure

Each test case should contain:

• Use case ID
• Test Case ID
• Short description
• Pre-Conditions
• Test Steps
• Test Data
• Expected Result
• Post Condition