about summary refs log tree commit diff stats
path: root/archive/1.vm/cannot_write_tests_for
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2020-01-01 17:04:37 -0800
committerKartik Agaram <vc@akkartik.com>2020-01-01 17:04:37 -0800
commit2a4088119cf41175457414dfa59bd4064b8f0562 (patch)
tree64fe184e399f9870ebd481a90eec34d51e5dff68 /archive/1.vm/cannot_write_tests_for
parent23fd294d85959c6b476bcdc35ed6ad508cc99b8f (diff)
downloadmu-2a4088119cf41175457414dfa59bd4064b8f0562.tar.gz
5852
Diffstat (limited to 'archive/1.vm/cannot_write_tests_for')
-rw-r--r--archive/1.vm/cannot_write_tests_for17
1 files changed, 17 insertions, 0 deletions
diff --git a/archive/1.vm/cannot_write_tests_for b/archive/1.vm/cannot_write_tests_for
new file mode 100644
index 00000000..444aafd5
--- /dev/null
+++ b/archive/1.vm/cannot_write_tests_for
@@ -0,0 +1,17 @@
+0. main's ingredients
+1. assertion failures or errors inside scenarios
+2. screen background color
+3. has-more-events?
+4. hide/show screen
+5. more touch event types
+6. sandbox isolation
+7. errors in reading/writing files (missing directory, others?)
+
+termbox issues are implementation-specific and not worth testing:
+  whether we clear junk from other processes
+  latency in interpreting low-level escape characters
+
+calls to update-cursor are currently duplicated:
+  render-all calls update-cursor to simplify testing
+  event-loop needs to call update-cursor explicitly to backstop branches doing their own minimal rendering
+  solution: update-cursor after minimal rendering