Confirmed users
174
edits
Test Pilot/UX Workflows: Difference between revisions
no edit summary
(Start Page) |
No edit summary |
||
| Line 1: | Line 1: | ||
== Test Pilot | == Reviewing and Maintaining Test Pilot == | ||
| Line 49: | Line 49: | ||
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'''. | 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 == | |||