Hi Patrick, How did you write unit tests for you custom lint rule? Is there an easy way to get started? I've only found documentation on how to test AOSP lint checks [1], not custom ones.
[1] - http://tools.android.com/tips/lint/writing-a-lint-check Thanks! Marius On Sunday, November 17, 2013 11:26:33 AM UTC-6, Patrick Hammond wrote: > > If you have custom lint checks that don't make sense to provide in the > core set of Android lint checks (they could be library specific, project > specific, team coding conventions, etc), you need to manually copy those > lint JARs to the current machine's lint tools settings directory (per > http://tools.android.com/tips/lint-custom-rules, under 'Register Custom > Jar File'). This doesn't feel very portable or flexible. What I'd like to > see is the ability to specify multiple custom lint checks in a project > configuration to get this portability and flexibility. > > Thinking it through: > > - This feature would probably start with being able to specify paths > to additional checks via the Lint CLI. > - Support for declaring checks as dependencies via Gradle and/or other > build scripts. > - Ideally, you wouldn't need to also update another project > configuration to specify inclusion of the checks. > - IDE support to manage declaring/managing the additional lint > checks (not sure what this looks like). > > All that said, is there a design reason or constraint that would make this > ill advised/impossible? Is it something already on the roadmap, or now on > the roadmap, and just needs some help? > > Thanks in advance! > Patrick > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
