Road trip to a wedding in Vegas.
I’ve been consumed by “testing” lately. Depending on the reader and project stage, tests help design, document and verify. I’ll come out with something nice about this soon - but it’s on ice! To assist, I’m porting and polishing my “code reformater” to Janet. This rearranges all code in different views e.g.
- happy path (main line of logic for main from beginning to end)
- debugging (1 level above and below the current func, along with its tests and various helper functions)
- feature extension (just collect everything which calls or uses this API)
From the human side, you have to tag some things e.g. mark with #GUI in a comment parts which deal with that concern/API, but mostly based on what calls other things, it just exposes parts of t…
Road trip to a wedding in Vegas.
I’ve been consumed by “testing” lately. Depending on the reader and project stage, tests help design, document and verify. I’ll come out with something nice about this soon - but it’s on ice! To assist, I’m porting and polishing my “code reformater” to Janet. This rearranges all code in different views e.g.
- happy path (main line of logic for main from beginning to end)
- debugging (1 level above and below the current func, along with its tests and various helper functions)
- feature extension (just collect everything which calls or uses this API)
From the human side, you have to tag some things e.g. mark with #GUI in a comment parts which deal with that concern/API, but mostly based on what calls other things, it just exposes parts of the AST in different linear orders. It puts everything in SQLie and can output everything into new files, to see in the IDE. Tagging the purpose and dates of various tests can do a lot here, I think.