Gno code coverage and plan improve it.

[AnhVAR]

Gno code quality status

We have analyzed and executed all the existing test cases for the Gno repository to evaluate the current status of the project. We observed that the average code coverage for the project is around 60%. There are several directories that either have not been tested or lack test code.

Source code have many issues detected by static analysis tool.

Based on our analysis, we believe that to enhance the quality of the project's source code, we can contribute the following actions:

1. Perform static testing for any code changes.
2. Fix bugs identified by static code analysis.
3. Write integration and unit test scripts to improve code coverage.
4. Set up continuous integration and continuous delivery (CI/CD) for the repository to ensure that test cases pass with each new code update.
5. Create Regression testing plan

[Nhatran94]

@dongwon8247 @moul @michelleellen pls take a look

[notJoon]

I'm gradually adding tests while working on the codebase. I definitely agree that a major improvement is needed.

[zivkovicmilos]

Hey @AnhVAR,

Thank you for opening up the issue 🙏

We are well aware of the coverage problem, and have internally dedicated a significant chunk of our time to tackling this problem, especially for critical code segments. Additionally, we've started setting up procedures and tooling with our security engineer @kristovatlas, so there are no show-stopping bugs.

I suggest we keep this issue open as an ongoing thread on the coverage progress

[thehowl]

See-also gnolang/gno#1215