Skip to end of metadata
Go to start of metadata

Yes, the code's quality is very important to us. The most tools bellow are already integrated on Encuestame project.

Tips
  • Out-engineer user-error as much as possible. "In other words," writes Schorr, "never trust that the user will do what you expect, especially when entering data."
  • Be open to including other languages and technologies where appropriate.
  • Don't reinvent the wheel.

Code's Quality Tools

Java Tools

There are several tools to measure the code quality. The ones I have tried with a lot of success are:

FindBugs – _uses static analysis to look for bugs in Java code_. This is a great tool, it discovered possible NullPointerExceptions and a lot more bugs in my projects

PMD - scans Java source code and looks for potential problems. The rules are configurable, but at the beginning you will only need the provided one (and spend a lot of time to choose your favourites ).

Checkstyle - Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java code to spare humans of this boring (but important) task. This makes it ideal for projects that want to enforce a coding standard.

Cobertura - Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage.

Javascript Tools

JSLint - Lint, you can check all your JavaScript source code for common mistakes without actually running the script or opening the web page.

There is the files. https://github.com/encuestame/encuestame/tree/development/encuestame-war/util

Eclipse Plugins

AnyEdit - AnyEdit plugin adds several new tools to the context menu of text- based Eclipse editors, to output consoles, to Eclipse main menu and editor toolbar. AnyEdit contributes also Import/Export working sets wizards.

Encuestame Integration Tools

Cobertura of Code

JUnit is used on entire of project, is a important part of quality of code, all lines of code should be covered as possible with jUnit integrated with Spring Framework Test Module.

http://www.junit.org/

Own test for Dojo's widget currently are missing, we need test all our widgets with this tool.

DOH - http://www.ibm.com/developerworks/web/library/wa-aj-doh/index.html

Labels: