5
edits
Labs/Test Pilot: Difference between revisions
m
→How to write a test proposal: fixed Ubiquity link
m (→How to write a test proposal: fixed Ubiquity link) |
|||
| Line 5: | Line 5: | ||
Test Proposal is a document providing information on a new test idea to the Test Pilot community. The test proposal should provide a concise goal either help solve a specific design question or discover user feedback for early-stage design experiments. | Test Proposal is a document providing information on a new test idea to the Test Pilot community. The test proposal should provide a concise goal either help solve a specific design question or discover user feedback for early-stage design experiments. | ||
=== How to write a test proposal === | === How to write a test proposal === | ||
Each test proposal must have: | Each test proposal must have: | ||
Please see the proposal example of [https://wiki.mozilla.org/Labs/Test_Pilot/Test_Proposals/Ubiquity | *A champion -- someone who writes the proposal, shepherds the discussions in the appropriate forums, and attempts to build community consensus around the idea. The champion (a.k.a. Author) should first attempt to ascertain whether the design question is test-able. Posting to <mozilla-labs-testpilot@googlegroups.com> is recommended. | ||
*Goals -- design questions you want to answer or explore by running this test. | |||
*Data type -- what kind of data will be required for this test. This is very important for a test proposal. Test Pilot program only runs tests that fully obey our [https://testpilot.mozillalabs.com/privacy.html/ Privacy Policy]. | |||
Please see the proposal example of [https://wiki.mozilla.org/Labs/Test_Pilot/Test_Proposals/Ubiquity Ubiquity] | |||
=== What happens after the test proposal === | === What happens after the test proposal === | ||