Confirmed users
400
edits
(Add reference to Robotium-4.2 upgrade bug) |
|||
Line 5: | Line 5: | ||
= Creating a new test = | = Creating a new test = | ||
The best way to create a new Robocop test is to copy and modify an existing one -- see mobile/android/base/tests. | The best way to create a new Robocop test is to copy and modify an existing one -- see mobile/android/base/tests. | ||
(We are currently upgrading our tests from Robotium 3.6 to 4.2 [{{bug|912590}}], so the APIs used in the tests may be out of date. It might be helpful to take a look at the [http://code.google.com/p/robotium/wiki/Changelog Robotium changelog] to see some of the new API methods.) | |||
Create a new file in the test directory named test[YourFeature].java.in. | Create a new file in the test directory named test[YourFeature].java.in. | ||
Line 20: | Line 22: | ||
</pre> | </pre> | ||
For convenience, you can also extend one of the provided abstract classes, like BaseTest. | For convenience, you can also extend one of the provided abstract classes, like BaseTest, PixelTest, or AboutHomeTest. BaseTest derives from ActivityInstrumentationTestCase2 but also provides a bunch of boilerplate and utility functions. | ||
<pre> | <pre> | ||
public class testMyFeature extends BaseTest | public class testMyFeature extends BaseTest | ||
Line 32: | Line 34: | ||
</pre> | </pre> | ||
If you extend | If you extend one of the provided abstract classes, the setUp() and tearDown() are provided for you, but you can still override them and do additional setup/teardown if needed; just make sure you call super.setUp() and super.tearDown() in your overiddes as necessary. | ||
Finally, add your new test file to the test manifest: mobile/android/base/tests/robocop.ini: | Finally, add your new test file to the test manifest: mobile/android/base/tests/robocop.ini: |