Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| These guidelines complement the [Processes](../processes/overview.md) section, which covers workflows and phases of development. Here, we focus on the craft: what your code should look like, how to test it, and the habits that make you a stronger contributor. | ||
|
|
||
| ## Guidelines Available |
There was a problem hiding this comment.
This might be quite repetitive. Instead of listing the available guidelines, just jump to the getting started section.
|
|
||
| Testing is the first line of defense against bugs and exploits. In systems that handle real value and compose across chains, tests aren't optional, they're how we sleep at night. | ||
|
|
||
| This guide explains how we test code in the Optimism ecosystem: the structure and conventions you must follow, what kinds of tests to write, how to organize them, and best practices for writing maintainable test suites. |
There was a problem hiding this comment.
If you are going to list the things in the guide, just go straight there. The paragraph above feels repetitive.
|
|
||
| These guidelines complement the [Processes](../processes/overview.md) section, which covers workflows and phases of development. Here, we focus on the craft: what your code should look like, how to test it, and the habits that make you a stronger contributor. | ||
|
|
||
| ## Guidelines Available |
There was a problem hiding this comment.
Guidelines Available are repetitive. Let's only keep the getting started part.
There was a problem hiding this comment.
In general, this file could be divided into different documents within a folder. It could be named 'Testing guidelines', the overview file should be the content until line 31. Then, you could divide the rest into different pages: Linting, file organization, Best practices.
|
Btw, please check the CI that is failling. |
2 participants
CLOSES OPT-1225