Closed paulbutcher closed 13 years ago
A better solution might be to re-organise AndroidProject and AndroidTestProject so that they both derive from a common abstract base class, which would avoid the need to override the actions. But this was a larger change than I felt comfortable proposing right now.
If you feel that this is a better way to go, let me know and I'll put something together.
thanks, this is good enough for now. i'd like to revisit testing soon, it would be cool if we could integrate with robospecs and generate everything needed in the project template.
At the moment start-emulator and start-device, as well as starting the main application, also starts the tests app. And the default test app (because it has no Activity) crashes as soon as it's started.
This change overrides start-emulator and start-device so that they're no-ops for an AndroidTestProject.