New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPIKE: Breakdown of code areas to investigate in first batch #12442
Comments
One of the places where ZK App commands are processed is Also there are almost no comments and the code is far from self-explanatory, so improving on that would also be worthwhile. |
Module |
In addition to that, unfortunately |
The objective of this spike is to get a good enough understanding of the code and tests in the new portion of the codebase to make a plan for how to break down the following investigation of how good our test coverage is.
We will need to look at the diff between
develop
andcompatible
to find the major new features (mostly, zkApps). We will want to create a list of new components, where they are in the codebase, and how large they are. With that, we can then create individual tickets to look at the test coverage of each of those.The text was updated successfully, but these errors were encountered: