Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | one bug I've repeatedly run into while testing with Moby Dick | Kartik K. Agaram | 2022-05-23 | 1 | -0/+1 |
| | | | | https://www.hogbaysoftware.com/posts/moby-dick-workout | ||||
* | disable all debug prints | Kartik K. Agaram | 2022-05-23 | 1 | -1/+1 |
| | |||||
* | snapshot | Kartik K. Agaram | 2022-05-23 | 1 | -1/+8 |
| | | | | Why the fuck is this so fucking hard? | ||||
* | bugfix: don't rely on Screen_bottom1 while scrolling | Kartik K. Agaram | 2022-05-23 | 1 | -1/+1 |
| | | | | | Setting up the test just right to test the thing I want to test was a rube goldberg machine of constants. | ||||
* | first successful pagedown test, first bug found by test | Kartik K. Agaram | 2022-05-23 | 1 | -1/+11 |
| | | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff. | ||||
* | one more implication | Kartik K. Agaram | 2022-05-22 | 1 | -0/+3 |
| | |||||
* | basic test-enabled framework | Kartik K. Agaram | 2022-05-22 | 1 | -5/+184 |
| | | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up. | ||||
* | rename | Kartik K. Agaram | 2022-05-22 | 1 | -0/+37 |