Quality Assurance Workflow

[discoverdefiteam]

The goal: Create a methodology to follow when testing changes are made to the core logic.

It would be a great opportunity to start thinking about a checks and balance system to ensuring that changes made to terp-core are non-breaking (unless required). This is largely inspired by Tendermints Quality Assurance.

Some things that might be included:

• Local chain testing scrips.
• Mock upgrade testing scripts [multi-node, multi-commit]
• Proper Documentation for all of this

[discoverdefiteam]

Looked around more, found some recent & great examples to follow:

• dependabot implementation link

[discoverdefiteam]

Another topic to implement is fuzz testing. https://www.synopsys.com/glossary/what-is-fuzz-testing.html

This can be found implemented in wasmd & currently we do not have implemented .