A place for talking about the Ethereum Virtual Machine on Farcaster.

Writing tests with Forge on a new codebase, and two approaches have significantly (IMO) increased readability and simplicity:

1. One function per test file
2. Contract and parameter state altered through modifiers, e.g.
  ```
  function test_foo() external whenParameterIsSet whenAModuleIsInstalled
  ```

Been slowly moving to BTT, the one file per function feels like overkill for smaller checks though

Full-stack and Solidity dev @ Axis Finance, OlympusDAO. Formerly: GuardianUI

Pro-tip: writing forge tests in VSCode with GitHub Copilot can be really easy if you:
- Write a list of conditions and outputs
- Write modifiers for each condition (in the style of branching-tree technique)

VSCode will then write each of the test cases in list order.

Smaller functions I tend to combine into a single file. wrt BTT, I found the tooling aspect of it cumbersome. A checklist of TODOs and Github Copilot works really well:

Smaller functions I tend to combine into a single file. wrt BTT, I found the tooling aspect of it cumbersome. A checklist of TODOs and Github Copilot works really well: https://warpcast.com/jem/0x3c8dcaf5

Been slowly moving to BTT, the one file per function feels like overkill for smaller checks though  https://x.com/paulrberg/status/1682346315806539776?s=46&t=0FLFA-Rcngh6xG6Bfm626g

Interesting! Will try these.

Surprised by 1 but curious to see it in practice. And 2 looks so so clean!