v0.46 QA Rolling Issue

[robert-zaremba]

v0.46 QA

This issue collects tasks happening in parallel to the SDK Core Development.

Scope of this task

• Every breaking change and new feature should be reported in a rolling UX issue. QA team should:
  • verify that the UX is good and input & output are well presented for the user
  • define a test scenario for integration tests and, depending on the resources:
    • develop integration tests themselves
    • create an issue for the development team to implement the new test scenario
    • perform manual testing
• Every migration should be tested on a backstage chain with real data.
• Defined and introducing test scenarios.
• Verifying user experience of a high quality.
  • We want to have acceptance tests! Document and list acceptance lists which are implemented and which are still missing.
• Testing chain upgrades for every new breaking change
  • defining automated tests assuring data integrity after an update.

Cosmos SDK contributors should update this task and by adding new feature they are developing in order to get a support from the QA team. It's a feature developer (not QA Team) responsibility to develop unit tests. It's QA team responsibility to assure good acceptance tests definition and implementation.

Checklist

Below is a rolling list of tasks to collaborate with the QA Team.

• refactor!: Keyring migration #9695 manual testing of keyring migration (keys migrate, keys list, keys show CLI commands)
• fix!: remove grpc query routing through tendermint #10045 Concurrent gRPC queries