fix startup test failures from the driver
Dependencies
- [2]
5WHW3IDOfix initialization errors using driver.love - [3]
ARYMNK52merge bugfix: show test failures - [4]
TSV3KPBRtweak format of test failures - [5]
ZKH2N6MNMerge text0 - [6]
36Z442IVback to commit 8123959e52f without code editing - [*]
3QNOKBFMbeginnings of a test harness - [*]
BJ5X5O4Alet's prevent the text cursor from ever getting on a drawing - [*]
DTBFNHJDmanual tests for the protocol with the driver
Change contents
- replacement in app.lua at line 141
error('There were test failures:\n\n'..table.concat(Test_errors, '\n'))Mode = 'error'Redo_initialization = trueError_message = 'There were test failures:\n\n'..table.concat(Test_errors, '\n')live.send_run_time_error_to_driver(Error_message) - edit in Manual_tests.md at line 124
Driver can connect to app that contains test failures on startup. - edit in Manual_tests.md at line 126[2.2076][10.1501]
driver, define a new test with an invalid assertion:```test_foo = function()check(nil, 'foo')end```Hit F4. The test fails.Quit the client app and restart. App shows an error.Edit `test_foo` in the driver and remove the error:```test_foo = function()end```Hit F4. The error disappears from the app and driver.* clone this repo to a new client app, clear its save dir, run it, run thedriver, define a new test with an invalid assertion:```test_foo = function()check(nil, 'foo')end```Hit F4.Quit the client app and restart. App shows an error.Hit F4 again in the driver (without fixing the error).The client app continues to show the error.* clone this repo to a new client app, clear its save dir, run it, run the