113 lines
4.5 KiB
Markdown
113 lines
4.5 KiB
Markdown
I care a lot about being able to automatically check _any_ property about my
|
|
program before it ever runs. However, some things don't have tests yet, either
|
|
because I don't know how to test them or because I've been lazy. I'll at least
|
|
record those here.
|
|
|
|
Initializing settings:
|
|
- from previous session
|
|
- from defaults
|
|
- default_map absent/present
|
|
|
|
* How the screen looks. Our tests use a level of indirection to check text and
|
|
graphics printed to screen, but not the precise pixels they translate to.
|
|
- where exactly the cursor is drawn to highlight a given character
|
|
- analogously, how a shape precisely looks as you draw it
|
|
|
|
Panning (test these at multiple zoom levels):
|
|
* When no node has cursor, arrow keys and pageup/pagedown pan surface around, preserving relative positions of nodes
|
|
* When a node has cursor in viewport, arrow keys move the cursor within the node, keeping cursor visible, panning surface if scrolling is needed
|
|
* Pageup/pagedown scroll a whole viewport height at a time if possible, but keep cursor visible if not possible.
|
|
* When a node has cursor, pageup/pagedown pan surface around
|
|
* Position a node with some area above viewport. Position cursor at topmost row on screen. Hit up arrow. Surface pans. Cursor doesn't hide behind menu bar.
|
|
* Increase/decrease zoom, pan around using cursor inside node. The box for the editor surrounds the entire editor.
|
|
* Increase/decrease zoom, pan around using cursor outside node. The box for the editor surrounds the entire editor. (not perfect yet)
|
|
|
|
### Protocol with driver; error-handling
|
|
|
|
* clone this repo to a new client app, clear its save dir[1], run it, run the
|
|
driver, add a definition:
|
|
```
|
|
on.draw = function()
|
|
end
|
|
```
|
|
Hit F4. No error.
|
|
Quit driver, quit client app. Restart client app. No error.
|
|
|
|
* clone this repo to a new client app, clear its save dir, run it, run the
|
|
driver, add a definition that draws to screen:
|
|
```
|
|
on.draw = function()
|
|
love.graphics.print('hello!', 50,50)
|
|
end
|
|
```
|
|
Hit F4. Client app shows 'hello!'
|
|
Quit driver, quit client app. Restart client app. No error. Client app shows 'hello!'
|
|
|
|
* clone this repo to a new client app, clear its save dir, run it, run the
|
|
driver, add a definition containing invalid Lua:
|
|
```
|
|
on.draw = function(
|
|
```
|
|
Hit F4. Driver shows an error under the definition.
|
|
Fix the definition:
|
|
```
|
|
on.draw = function()
|
|
end
|
|
```
|
|
Hit F4. The error disappears.
|
|
|
|
* clone this repo to a new client app, clear its save dir, run it, run the
|
|
driver, add a definition containing invalid Lua:
|
|
```
|
|
on.draw = function(
|
|
```
|
|
Hit F4. Driver shows an error under the definition as before.
|
|
Quit the client app.
|
|
Restart the client app. It loads up without error.
|
|
Switch back to the driver. Fix the definition.
|
|
```
|
|
on.draw = function()
|
|
end
|
|
```
|
|
Hit F4. The error disappears.
|
|
|
|
* clone this repo to a new client app, clear its save dir, run it, run the
|
|
driver, add a definition containing invalid Lua:
|
|
```
|
|
on.draw = function(
|
|
```
|
|
Hit F4. Driver shows an error under the definition as before.
|
|
Quit the client app.
|
|
Switch back to the driver. Hit F4. The driver hangs and needs to be
|
|
force-quit. [This is not ideal, but how things are today.]
|
|
|
|
[1] We never clear the app from the driver's config. driver.love needs to be
|
|
robust to apps changing out from under it.
|
|
|
|
### Other compromises
|
|
|
|
Lua is dynamically typed. Tests can't patch over lack of type-checking.
|
|
|
|
* All strings are UTF-8. Bytes within them are not characters. I try to label
|
|
byte offsets with the suffix `_offset`, and character positions as `_pos`.
|
|
For example, `string.sub` should never use a `_pos`, only an `_offset`.
|
|
|
|
* Some ADT/interface support would be helpful in keeping per-line state in
|
|
sync. Any change to line data should clear line `fragments` and
|
|
`screen_line_starting_pos`.
|
|
|
|
* Some inputs get processed in love.textinput and some in love.keypressed.
|
|
Several bugs have arisen due to destructive interference between the two for
|
|
some key chord. I wish I could guarantee that the two sets are disjoint. But
|
|
perhaps I'm not thinking about this right.
|
|
|
|
* Like any high-level language, it's easy to accidentally alias two non-scalar
|
|
variables. I wish there was a way to require copy when assigning.
|
|
|
|
* I wish I could require pixel coordinates to be integers. The editor
|
|
defensively converts input margins to integers.
|
|
|
|
* My test harness automatically runs `test_*` methods -- but only at the
|
|
top-level. I wish there was a way to raise warnings if someone defines such
|
|
a function inside a dict somewhere.
|