Testing prototypes
Table of Contents
1. Summary
Working through a test scenario in the browser, seeing what waits for a tester, and browsing the agile tree.
2 prototypes answer to this group. Each one is a static page under
doc/prototypes/, opens with no build and no session, and reads mock data
only. The table below opens each one and says what it argues. Where a
prototype carries a Gemini review, the last column opens it: a review is a
generated alternative kept beside the agreed design, never instead of it.
Prototypes is the top page and the only inventory.
2. The prototypes
| Prototype | What it argues | Open it | Review |
|---|---|---|---|
| Test scenarios | A tester's two screens: the queue of scenarios waiting and done, and the runner that works through one. The runner is steps beside the detail, one step at a time, or the whole scenario as a document. Every variant states that nothing reads or writes a scenario yet. | prototype | none |
| Agile browser | The Development area gains a sprint board, a backlog and sprint charts. The board is columns of stories or a list, with a card detail, a filter bar, tiles and a strip of work trees. Any doc opens by its link. Every variant states that nothing reads the agile tree yet. | prototype | none |
3. Adding a prototype
Create doc/prototypes/testing/<name>/ with an index.html, and a
prototype.css and prototype.js when it needs them. Open the page with
the links table every prototype carries, and leave its review row at
none. Add a row to the table above, with the design note beside the
prototype when there is one. Stop there: the site build finds every
prototype under this tree, so no build file names it.