mu/cannot_write_tests_for

0. main's ingredients
1. assertion failures or errors inside scenarios
2. screen background color
3. more touch event types
4. sandbox isolation
5. errors in reading/writing files (missing directory, others?)

termbox issues are implementation-specific and not worth testing:
  latency in interpreting low-level escape characters
3629 - refcount commandline args 2016-11-06 07:48:31 +00:00			`0. main's ingredients`
3140 Manual tests for parse errors because scenarios can't handle assertion failures yet. 2016-07-23 21:17:35 +00:00			`1. assertion failures or errors inside scenarios`
			`2. screen background color`
3844 Once I start optimizing most events to not repaint everything there's no need to be smart about queued-up events. 2017-05-06 21:54:26 +00:00			`3. more touch event types`
			`4. sandbox isolation`
			`5. errors in reading/writing files (missing directory, others?)`
2141 - attempt to deal with slow networks On slow networks sometimes escape sequences were being partially consumed, causing junk to be added to the editor when you pressed arrow keys and so on. Now we have a way to wait. Empirically seems to work if I page-up and then scroll back up using up-arrow. Before I'd consistently get junk even on my local machine. Now I no longer do. If we still see problems I'll increase the wait time and see if the increase helps. Then we'll know more about this approach. 2015-09-04 18:07:08 +00:00
			`termbox issues are implementation-specific and not worth testing:`
			`latency in interpreting low-level escape characters`