Normally it is better to name test suite packages like test.com.example.phones
, adding test.
prefix to the package name. This allows to run, relocate or move all tests very easily in one go. If it is important to care about device-specific tests, another approach would be like test.phones.com.example
and test.tablets.com.example
.
While it is also possible to have test suites, these are often redundant. The most frequent test types are running all tests for the package being tested and running all tests available. If the test packages mirror the main packages, such runs can be easily launched from IDE that provides features to run all tests in a folder/package (right click and select "run as Android test" in Eclipse). And during automated builds in the cloud usually all tests must run anyway.
If you have more tests, not a bad idea is to create a separate testing project.