# QA Wishlist / Plan

- Desired release pipeline
- CI
- fix flaky e2e tests
- convert some e2e to integration tests
- much faster when possible
- bypass P2P network that is setup in e2e test env
- can remove lots of headaches regarding waiting for epochs to happen
- at least duplicate some e2e tests in the integration env
- Trigger devnets
- Automated load testing
- Existing load tester repo: https://github.com/heliaxdev/namada-scenario-tester/tree/master
- Pre-defined scenarios and randomized scenarios that can submit transactions to the chain
- Expand breadth of existing scenarios
- Can specify tx domains of interest
- Ex: I just want to test IBC and MASP - send only these txs
- If someone wants to manually test some scenario of txs in a devnet, they should generate a scenario json file so that it can be run on all future devnets
- Guide running commands as the validators / accessing their keys
- Set up both validators and full nodes
- Set up an external IBC chain and open connections
- Set up nodes that can run different / specified versions of the software
- check to see if new software is truly backwards-compatible
- Dedicated docs update for each release that is reviewed by >= 1 engineer with knowledge of the release contents
- Guides
- perhaps a Slack channel dedicated to this, as a hackmd repository
- every time a devnet is spawned, place a reply message containing a hackmd that explains how to interact with the devnet on your own
- Timely updating of open PRs for rebase / compatibility with new software versions
- Other notes
- revive devnet faucet and document usage
- finish setup of code coverage
- ChatGPT / LLM review of Rust code??
- https://github.com/anc95/ChatGPT-CodeReview
- https://antithesis.com/product/demo/
- https://antithesis.com/docs/getting_started/setup.html

- What to do in terms of testing for phase 1?
- Transaction load tester
- Internal testnets
- Gavin-coordinated testnets
- p

- Overarching priorities
- automation
- clear to use all available tools for any PR, not just draft / releases
- repurpose most of manpower for testing development for some time

- Notes on outlook
- Short term
- increase code coverage with unit tests
- follow coverage files output from CI runs
- solve immediate SE halt issues and test
- Medium term
- Content written above for QA pipeline improvements
- Longer term
- code refactors that don't really change functionality
- larger features