Merge text.love
This commit is contained in:
commit
4e19e609ba
|
@ -3,14 +3,11 @@ 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.
|
||||
|
||||
Startup:
|
||||
- terminal log shows unit tests running
|
||||
|
||||
* Initializing settings:
|
||||
- from previous session
|
||||
- Filename as absolute path
|
||||
- Filename as relative path
|
||||
- from defaults
|
||||
- from previous session
|
||||
- Filename as absolute path
|
||||
- Filename as relative path
|
||||
- from defaults
|
||||
|
||||
* 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.
|
||||
|
@ -38,8 +35,8 @@ Lua is dynamically typed. Tests can't patch over lack of type-checking.
|
|||
* 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 integers. The editor defensively
|
||||
converts input margins to integers.
|
||||
* 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
|
||||
|
|
Loading…
Reference in New Issue