Rooting may help you achieve a few otherwise difficult-to-simulate scenarios, but it comes with its own baggage that can weigh down potential benefits. Testers have to carefully weigh the pros and cons and the true need to root a device for a testing assignment before doing so.

Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day!

For distributed teams, activities usually get scheduled based on constraints such as availability and time zone, but people don’t often take into account when the most effective time to meet would be. Neglecting people’s work tendencies and schedule preferences could make it harder for the team to be successful.