Confirmed users
4,378
edits
B2G/QA/Tips And Tricks Part2: Difference between revisions
→General Manual Testing
(Created page with "= General Manual Testing = == General == * create a new profile ** you can even create a new user account (ie flash the device, adb shell rm -r /data/mozilla/b2g ; reboot devi...") |
|||
| Line 5: | Line 5: | ||
* repeating a tests while the device is running multiple times | * repeating a tests while the device is running multiple times | ||
** sometimes bit shifting could cause memory corruption; doing this through automation and checking the results to see if you're getting the same thing makes more sense to do. Not really recommended through manual as it becomes tedious... but you can. | ** sometimes bit shifting could cause memory corruption; doing this through automation and checking the results to see if you're getting the same thing makes more sense to do. Not really recommended through manual as it becomes tedious... but you can. | ||
* Use a debug build of some sort (like engineering) | |||
** do adb logcat while testing. Sometimes you can find asserts or crasher warnings pop up in the logcat. | |||
** you may need to turn on some other debug prefs. | |||
== Graphics == | == Graphics == | ||
=== General === | === General === | ||
| Line 12: | Line 15: | ||
* double tap | * double tap | ||
** just like in Zombieland, that extra tap just much help do the trick. | ** just like in Zombieland, that extra tap just much help do the trick. | ||
* long tap | |||
** context menus should pop up... and then there's times when they should not. | |||