|
|
| Line 1: |
Line 1: |
| = Mobile Test Plan =
| | {{warning|The original Mozilla Labs Test Pilot project has been retired. Click the 'View History' link on this page to read the old content.}} |
|
| |
|
| # Install the add-on from http://people.mozilla.com/~jdicarlo/tpm.xpi onto Fennec on an Android phone.
| | As of January 2016 a similar initiative, formerly named Idea Town, has been [http://micropipes.com/blog/2016/01/27/meet-the-new-test-pilot/ named Test Pilot]. |
| # Upon first-run, you should see a Welcome page. Make sure the page looks good and fits on the mobile screen, and that the links work.
| | |
| ## The next time you start up, the welcome page should not reappear. It's only supposed to appear once. If you want to force it to appear again in order to test it again, go to about:config and reset the pref extensions.testpilot.lastversion.
| | '''[[Test_Pilot|Learn more about the new Test Pilot!]]''' |
| # Go to the add-ons manager and make sure Test Pilot appears there.
| |
| # Click Test Pilot, then click Options. You should see the following options:
| |
| ## Run User Studies (default to Yes)
| |
| ## Automatically Submit (default to No)
| |
| ## See All Studies (button)
| |
| # Click See All Studies. You should go to a page that says "All Test Pilot Studies" which lists studies called "Mobile Example" and "Mobile Heatmap"
| |
| # Click on the title "Mobile Example".
| |
| # This should take you to a page that says "Thank you, Test Pilot!" and describes the Mobile Example study in progress.
| |
| ## You should be able to click the hide/show buttons for different subsections of the page (usage data, privacy info, contact info) to fold and unfold them
| |
| ## In the usage data section there should be a bar chart here with two bars on it, which should be clearly labeled as "back button" and "forward button" and should be accurate counts of the number of times you hit each button since the study started. (Please test the accuracy by using the forward and back buttons in Fennec a few times and making sure the count is correct for both.)
| |
| ## Make sure the links in the contact info section work.
| |
| ## The "Mobile Example" title link should take you to a web page on the Test Pilot site describing the study, which should open in a new tab. (This is currently an invalid URL, so a new tab will open but not take you anywhere useful.)
| |
| ## The "Raw Data" link should take you to a page where the raw data is displayed in tabular form. The data on this page should match the data shown in the graph on the study page. (hit the back button to get out of here).
| |
| ## The "Quit this study" link should take you to a page where you can optionally enter a reason, and then click "Quit the Study" which should take you to a page letting you know that the study is canceled.
| |
| # If the study is canceled, it should appear at the bottom of the "All Test Pilot Studies" page, with an icon to clearly indicate it's canceled. And it should no longer be collecting data, obviously.
| |
| # Assuming you don't cancel the study, the study should prompt you to submit when it finishes its run. You can test this by forcing the study to end, like so:
| |
| ## Load chrome://testpilot/content/debug.html
| |
| ## Make sure "mobile example" is selcted in the dropdown menu in the upper right
| |
| ## Where it says "set it to", pick "4 (Finished)".
| |
| # This should produce an Android notification, with a puzzle-piece icon, that says that the mobile experiment study is finished running. Check that it's legible. When you click on the text in the notification, it should take you to the Mobile Example Study detail page, which should now display a message that the study has finished collecting data. There should be a green button saying "Submit".
| |
| ## The message in the Android notification should take up only one line.
| |
| ## If you already have the study detail page open in another tab, then when you touch the notification it should switch you to that tab instead of opening another one.
| |
| ## (If you go to the Mobile Example Study detail page by the method described in step 6, then it should look the same way, with a green "Submit" button.)
| |
| # If you click the submit button, then a few moments later (assuming you have an internet connection so the upload succeeds) the page should change to tell you about the successful upload.
| |
| ## A submitted (or canceled) study should no longer display the "Quit this Study" link.
| |
| ## After submitting the study you should still be able to scroll the screen and swipe to see the Fennec sidebar UI (there was a bug before where it would freeze on this screen).
| |
| # After submitting or canceling the study, here's how to reset it for more testing:
| |
| ## Load chrome://testpilot/content/debug.html
| |
| ## Make sure "mobile example" is selcted in the dropdown menu in the upper left
| |
| ## Click "Reset Task"
| |
| ## Click "Reload All Experiments".
| |
| ## The Mobile Example study should now be back in the running state -- you can check this by looking at the Mobile Example Study detail page and verifying that the text says it's in progress. From here, you can test cancellation and/or submission again.
| |
| # Test the auto-submit option:
| |
| ## Turn the "automatically submit" pref on, using the test pilot options panel on the add-ons manager.
| |
| ## Reset the study using the steps described above.
| |
| ## Let the study collect some data (hit forward and back a couple of times)
| |
| ## Trick the study into thinking it has ended by editing its start date: Go to about:config, find the preference called extensions.testpilot.startDate.mobile_example_2. Edit it to be one week earlier than it is (the exact date doesn't matter, but 1 week is easiest since you won't have to change the day of the week).
| |
| ## Back on the debug page, click "Reload All Experiments".
| |
| ## You won't see a notification, but the study should have silently submitted. You can test that this worked by loading the Mobile Example Study detail page and checking that it has a message saying "thank you for submitting your data".
| |
| # To test the new metadata collection: Go to chrome://testpilot/content/debug.html then choose a study from the drop-down menu in the upper-left. (If this drop-down menu is empty, wait a few seconds and then reload the page.) Click "show metadata"; you'll see a bunch of JSON data barfed to the screen. Scroll down past the accessibility preferences and look for the system info, especially "sysinfo-arch", "sysinfo-name", and "sysinfo-version". These should show the correct values for the processor type of your phone, the OS name, and the OS version respectively.
| |