We need to design a baseline test that we can reuse perpetually #489
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, I come up with ideas for throwaway games and apps when I need to test braid end to end. This works well enough, but I'd like to put more thought into it. Mainly, we should devise a test that creates basic implementations of an array of different types of applications.
Some ideas:
This requires some research and design work to round out the types of things we want Braid to be good at. The end result should be a single brief that builds one project and tests all of these types of projects we want to judge Braid on, as well as testing as many of Braids features as possible.
Shipped in cmoriarty/braid#490 (main
799b2f05), archived in cmoriarty/braid#491 asstandard-test-run. The capability isstandard-run.docs/test-briefs/midway.md. Midway is a small arcade with a scoreboard, in eight parts that do not depend on each other: a static lobby, a 2D pixel-art game, a number puzzle, a 3D game, a game for two people, a database application with an API, a page of charts, and a background worker. Each asks for a phone-width screen. Nothing calls an outside service, and everything random or timed takes a seed or a clock../tools/standard-run.sh <server> <n>starts a New Project run inbraid-testing/midway-<n>: the thorough pipeline in one run, groups side by side, auto-approve on, Use CI off, the brief's back end as the run's services.docs/testing.mdlists the rows written down for every standard run, and says when to use Midway, Greeter or Scratch.Design choices are in the archived change's
design.md, among them why one arcade and not eight programs, and why the parts are independent (side-by-side groups need work that does not chain). Not covered yet: a planned, several-run variant; a run with CI on; a Free run. Each is this brief with one setting changed.The first run is next; its record and findings go on its own issue.