Tools that can help in code checking in Android

Question

Is there any good tools or Eclipse Plugins that would scan my Android Project and identify possible 'Memory leaks', susceptible code for 'Force closes' and other general code standards of Java and/or Android.

score 2 · Accepted Answer · answered Sep 15 '12 at 07:52

2

One good tool is the "LINT" Tool Available in Eclipse + Android-SDK.

http://tools.android.com/tips/lint

Another good find was "FindBugs" that locates Java Bugs and suggests enhancements.

http://findbugs.sourceforge.net/
http://findbugs.cs.umd.edu/eclipse/

Is there any other tool that you'd suggest ?

answered Sep 15 '12 at 07:52

Brighton Vino

295
3
10

Were you really interested in any answers to your question? You answered the same minute that you asked the question, which seems basically impossible for the answer above without having it prepared in another editor... – Bananeweizen Sep 19 '12 at 17:47

score 2 · Answer 2 · answered Sep 15 '12 at 08:00

2

This doesn't answer the question but does offer an alternative.

In my opinion, Intellij IDEA is better than Eclipse in almost every way. Its' code inspectors in combination with Android Lint and Findbugs is powerful. The way IDEA finds, reports and visualises possible bugs, "code smells" and suggestions for refactoring is superb. I'm not aware of any IDE that does the job as well.

answered Sep 15 '12 at 08:00

Simon

14,407
8
46
61

I'm looking for a solution within Eclipse. I don't want to be looking at a new IDE right now. Thanks for the suggestion for an alternative IDE. – Brighton Vino Sep 15 '12 at 08:18

score 2 · Answer 3 · edited May 23 '17 at 11:55

2

Besides android-lint, which is already available in your installation of the ADT and finds Android specific issues, I recommend both Findbugs and CodePro Analytix for standard Java code checks.

edited May 23 '17 at 11:55

Community

1
1

answered Sep 16 '12 at 05:44

Bananeweizen

21,797
8
68
88

score 2 · Answer 4 · answered Sep 16 '12 at 06:32

A force close is just any uncaught exception in you code, such as a NullPointerException. You can debug these issues as they occur by reading the stack trace output to logcat.

For memory analysis I suggest you start by watching Memory management for Android Apps (a session from Google I/O 2011) and read the companion blog post Memory Analysis for Android Applications. They provide some good suggestions for strategies and tools to debug memory leaks and other issues.

Tools that can help in code checking in Android

4 Answers4