Gregory's Server
Dealing with failing tests when all you have is a map for code
Mechanisms:
* Highlight tests in green.
* Run all tests on any change.
* Highlight failing test cases in red.
* Turn edges of vision red when there's any failures, just in case failing tests are out of view.
* Hotkey to zoom out over all of current view.
* Same hotkey to restore viewport settings.
* Click anywhere to zoom in.
https://git.sr.ht/~akkartik/driver.love
(What is a "freewheeling" app? http://akkartik.name/post/roundup22)
Some distilled reference documentation on my Freewheeling Apps (a way of building low-maintenance Situated Software for small groups)
In a bare-bones template repo (~500 LoC): https://codeberg.org/akkartik/template-live/src/branch/main/reference.md
In a more elaborate template with testable primitives and an editor widget: https://codeberg.org/akkartik/template-live-editor/src/branch/main/reference.md
Open it on a browser tab when you clone and start editing using https://git.sr.ht/~akkartik/driver.love. There are a few examples in the Readme to spark ideas. Works on any Windows and Unix.
Some distilled reference documentation on my Freewheeling Apps (a way of building low-maintenance Situated Software for small groups)
In a bare-bones template repo (~500 LoC): https://codeberg.org/akkartik/template-live/src/branch/main/reference.md
In a more elaborate template with testable primitives and an editor widget: https://codeberg.org/akkartik/template-live-editor/src/branch/main/reference.md