Details
-
Suggestion
-
Resolution: Won't Fix
-
None
Description
It's always hard for us to say no to our customers. However, design decisions are not only about "Do we want to have this feature?" but also "Is this a best feature we can implement using our available resources?". We want to invest our time in making your lives (and code!) better. The fact that Google are building their Android IDE based on IntelliJ IDEA, which has a built-in coverage tool, means that you can measure code coverage for your Android apps, in an environment supported by Google. Therefore, we decided to not implement Clover for Android in the near future. Beginning of Clover 4.1 release, we will remove all documentation related to Clover for Android prototype and close the related issues.
Fully functional support for Android platform using Eclipse ADT, including:
- instrumentation of application and test code, including automatic packaging of Clover Runtime into JAR
- running on a device or emulator
- transferring coverage files from a device/emulator back to PC to Eclipse IDE (including refreshes of Clover views)
- cleaning coverage files on a device/emulator
- cross-project unit testing (required by ADT)
Attachments
Issue Links
1.
|
Restructure Clover modules |
|
Closed | Marek Parfianowicz |
2.
|
Android support in Clover-for-Eclipse |
|
Closed | Marek Parfianowicz |
3.
|
Write integration tests |
|
Closed | Marek Parfianowicz |