Test Pilot has three main features
- Targeted new feature deployment (including UI modification) with rollback and cleanup.
- Targeted links to external content (surveys, in practice, but could be links to prototypes)
- Observation, monitoring, upload of user event activity.
SMOKE Current Crisis: Test Pilot is breaking bc on linux-64 opt builds.
FIRE (real crisis): Test Pilot is old and creaky, with poor testing, build practices, and documenation.
We are sick of smoke, and want to put out the fire!
We have two proposed fix plans:
-
Keep most of the Test Pilot 1 semantics / behaviours, and DOCUMENT THEM.
-
make Test Pilot restartless, for the amo version
-
elminate all 'cuddlefish' modules, and replace them with current jetpack modules.
-
add tests for at least some of the DOCUMENTED behaviors / expectations
-
run proper code coverage testing (on the addon version, using techniques a la: https://gist.github.com/gregglind/3900355), and attempt to reach 100% coverage.
-
(optional) move "Feedback" into a seperate addon / xul overlay / built-in as appropriate (See SIMPLER FEEDBACK, below)
-
timeline
- two weeks to build
- landing?
-
see: https://github.com/gregglind/git-testpilot/commits/jetpack
- already restartless
- de-cuddlefish-ed
- Needs xul portings, debug screen, notification boxes, etc (in progress)
- Jetpack team builds 2.0, with possibly new semantics
- Also restartless, has tests, code coverage
- Drawback: Won't start building until April! (so, in M-C in May? June?)
As a side project, SUMO has given soft approval for simplifying the 'feedback' button to just be a link to http://feedback.mozilla.org/, rather than having sub-sections. This code could move into browser.xul etc, as appropriate, and be de-bundled from Test Pilot
- UX-Research as approved 80+ hours for me to do the 1.3 plan
- SUMO has approved a 'simpler feedback button