[SPIKE] Document Localnet feature paths for E2E tests

[jessicadaugherty]

Objective

Improve and expand the definition of E2E localnet test paths for stress, chaos, and other types of testing to ensure the robustness of the network. A set of well-defined test paths will enable the team to identify potential weaknesses and improve the overall stability before deploying to testnet.

Origin Document

MVT Features

Goals

• Harden V1 for testnet by identifying and addressing potential vulnerabilities and weaknesses.
• Establish a comprehensive set of test paths for each module, covering various scenarios and edge cases.

Deliverables

• Review the current test paths and note any areas for improvement or gaps in coverage here.
• Enhance existing feature paths with more detail and clarity, ensuring they comprehensively cover each module's feature sets.
• Identify and document additional test scenarios, including edge cases, potential vulnerabilities, and stress/chaos scenarios, for each module.
• Outline testing priorities per module

Non-goals / Non-deliverables

• Designing or writing tests

General issue deliverables

• Update the appropriate CHANGELOG
• Update any relevant READMEs (local and/or global)
• Update any relevant global documentation & references
• If applicable, update the source code tree explanation
• If applicable, add or update a state, sequence or flowchart diagram using mermaid

Testing Methodology

• All tests: make test_all
• LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

---

Creator: @jessicadaugherty

[jessicadaugherty]

Repurpose into spike for chaos and stress testing

[jessicadaugherty]

Note to self: discuss guidelines with team (and ownership):

• Design best practices
• Avoiding redundancies/modular tests
• Data sources
• Prioritization
• Automation
• Frequency
• Reporting standardization

[jessicadaugherty]

Iteration 15 Planning: @team please check criteria. Lmk if we should have a more explicit deliverable re: scenario coverage (e.g. if the goal should be just to identify paths for must have testnet features)

[Olshansk]

Iteration 15 Planning: @team please check criteria. Lmk if we should have a more explicit deliverable re: scenario coverage (e.g. if the goal should be just to identify paths for must have testnet features)

I think the deliverables are still a bit too ambiguous and broad, especially because V1 E2E Paths ended up being more of a brainstorming workshop of how to write tests using LLMs rather than defining actual test cases.

Going to think about it for another day or two and update by EOW.