Test Pilot/UX Workflows: Difference between revisions

← Older edit

Test Pilot/UX Workflows (view source)

Revision as of 00:56, 30 January 2019

381 bytes removed , 30 January 2019

no edit summary

Marniepw

29

edits

@@ Line 1: / Line 1: @@
+== The Test Pilot program ended in January 2019. ==
+'''To read more, please see: [https://medium.com/firefox-test-pilot/adios-amigo-51bec2a00072 Adios, Amigos]. The information below is being retained for posterity. Thanks to all who traveled along with us!'''
 == Reviewing and Maintaining Test Pilot ==
@@ Line 47: / Line 50: @@
 Taking this core job a step further, '''what you should really be doing is paying attention to ongoing work in the current sprint and ensuring that things look like they should as they’re being built.''' In general this will mean keeping an eye on the Test Pilot dev server (which shows the latest master branch), but you can also get involved by reviewing Pull Requests in Github. For example, don’t be afraid to ask engineers for screenshots of their work, so you can give them pointers about things they may have missed while things are still being worked on. If you see a problem with a pull request while it’s under review '''SAY SOMETHING IN THE PULL REQUEST''' If you see an issue with UI on the Dev server '''FILE AN ISSUE'''.
-== Proposing New Features For Test Pilot ==
-== Building Specs for New Features In Test Pilot ==
-== Assisting in Test Pilot User Research ==
-The Test Pilot team is interested in interviewing people who have used Test Pilot in order to improve the experience. Interviews will take place over video conference in February 2017. If you're interested in participating, please fill out this [https://www.surveygizmo.com/s3/3306646/Interivew-Study-About-Firefox-Test-Pilot survey], and we'll get back to you if you're a fit for the study. Please direct any questions about Firefox User Research to: '''sharon@mozilla.com''' or '''sharon''' on IRC.