Better testing infrastructure

We have, so far, written a minimal amount of tests in order to focus on rapid prototyping without major concern for breakage, in the absence of actual users. As the scope of the project grows, the permutations of cases where regressions can crop up is making it harder to detect bugs purely by hand. Users might also care about stability, even though 0.1 is alpha.

We should build testing infrastructure to help create tests. Thanks to the project architecture which is split between the Editor Frontend, Editor Backend, Graphene, and (eventually) Charcoal, with the message dispatch system tying them together, it should be pretty easy to write tests in general by writing many tests using messages. Some infrastructure can include a way of recording messages for easy copy and paste into tests, thereby turning manual tests into automated tests.

This issue can serve as a good place to discuss other forms of testing infrastructure to help make it easy to write and maintain efficacious tests.

该 issue 没有指出任何文件或测试。首先查看 Editor Frontend、Editor Backend、Graphene 和消息分发系统，然后检查现有的最小测试设置。完成的标准是确定一套双方认可的测试基础设施，并找到一种切实可行的方法，将基于消息的手动检查转换为自动化测试。

由索引模型根据 Issue 内容生成。