[E2E] Test coverage for select CLI features

[dylanlott]

Objective

This issue covers the work for testing the select features of the Pocket binary.

Origin Document

#466 is the umbrella ticket for the E2E suite. #580 creates the harness for that test suite but was explicit about not including a comprehensive test suite, only the foundation of one. This ticket addresses the test cases and features under test.

E2E Testing Framework

Goals

• Determine if and how we can measure test coverage
• Get decent coverage for happy path and error path tests for select CLI features

Deliverable

The following features are selected for test coverage.

• [ ] Account
• [ ] Application
• [ ] Consensus
• [ ] Fisherman
• [ ] Governance
• [ ] Node
• [ ] System
• [ ] Validator

Non-goals / Non-deliverables

• No flakey tests
• Not supporoting failiing tests

General issue deliverables

• [ ] Update the appropriate CHANGELOG(s)
• [ ] Update any relevant local/global README(s)
• [ ] Update relevant source code tree explanations
• [ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

• [ ] Task specific tests or benchmarks: make test_e2e
• [ ] New tests or benchmarks: make ...
• [ ] All tests: make test_all
• [ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

---

Creator: @dylanlott Co-Owners: @Olshansk

[Olshansk]

@dylanlott The deliverables of this ticket are not very clear to me. Is the goal:

1. To document a list of tests that will be covered for all the actors (not and future)?
2. Automate testing for everything currently exposed by the CLI?
3. An umbrella ticket that will help capture and define downstream work?