docs: the one page a tester actually reads - #121
Merged
Merged
Conversation
The testers are ready, and what existed until now was a protocol written for the product owner (Phase 2, three falsification lines, weekly data) and a session-handoff document. Neither is something you can forward to a creator. This is that page: what the tool is in one line, how to start with three concrete paths, and the five questions worth answering — with the fourth being the "without this I wouldn't have posted it" moments, since that is the line the Phase 2 decision actually rests on. It also lists what is already known (modelling takes seconds, publication is manual by design, the nightly switch is off by default) so testers do not spend their first week reporting it, and states plainly what happens to their data.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The testers are ready, and what existed until now was a protocol written for the product owner (Phase 2, three falsification lines, weekly data) and a session-handoff document. Neither is something you can forward to a creator.
This is that page: what the tool is in one line, how to start with three concrete paths, and the five questions worth answering — the fourth being the "without this I wouldn't have posted it" moments, since that is the line the Phase 2 decision actually rests on.
It also lists what we already know (modelling takes seconds, publication is manual by design, the nightly switch is off by default, mobile is still being polished) so testers do not spend their first week reporting it, and states plainly what happens to their data.