Comments for page "Cool Tools"

Findbugs

Mon, 09 Jun 2008 23:27:29 +0000

I find Findbugs really useful ++++

Scriptella is great

Wed, 28 May 2008 13:24:15 +0000

We used Scriptella to move select data from a Microsoft SQL Server DB to a MySQL DB. It has worked great and was able to handle many complex use cases. It saved us a lot of time. The support from the author is great. I am very impressed.

StackTrace

Thu, 20 Mar 2008 22:29:24 +0000

StackTrace from http://www.adaptj.com for monitoring and production mode debugging.

Cobertura is Test Coverage

Sat, 15 Mar 2008 06:39:17 +0000

I think Cobertura is Test Coverage instead of Testing

Scriptella ETL

Thu, 06 Mar 2008 13:38:04 +0000

We use Scriptella ETL to import test data in CSV format. Scriptella is also used to initialize an in-memory database for jUnit tests.

jTrac for Issue and Task Tracking

Fri, 29 Feb 2008 06:11:14 +0000

We are using jTrac to track issues and task at Acclaris (www.acclaris.com). We have offices in Tampa, Kansas City in USA, Kolkata, Vizag and Siliguri in India. With jTrac it is very easy to setup multiple workspaces and define your own customized workflow and custom fields for each workspace. It deploys as a war file.

moc.siralcca|eejrenab.hbaruas#moc.siralcca|eejrenab.hbaruas

jWebUnit and HttpUnit

Fri, 29 Feb 2008 06:00:37 +0000

We started writing functional tests using HttpUnit and later migrated to jWebUnit. I believe these are worth mentioning in your book.
thanks,
moc.siralcca|eejrenab.hbaruas#moc.siralcca|eejrenab.hbaruas

Scriptella

Sun, 17 Feb 2008 20:54:39 +0000

I've successfully used Scriptella to migrate from MySQL to DB2 and PostgreSQL. It works fine.

Cruisecontrol

Tue, 27 Nov 2007 15:28:25 +0000

Cruisecontrol could be an interesting topic for the book.

Monitoring Build Statistics

Mon, 25 Jun 2007 06:53:57 +0000

Hi,

to monitor quality statistics for project, i'm using :

- http://mojo.codehaus.org/dashboard-maven-plugin/: a Maven 2 plugin written by me for a single project (with or without multi-modules
- http://sonar.hortis.ch/ : a Maven 2 plugin + a Jetty application to monitor all projects for a company

Hibernate plugin for Eclipse

Fri, 22 Jun 2007 01:09:36 +0000

For those coding Hibernate in Eclipse, they have got
to try out Hiberante plugin as described from

http://www.hibernate.org/Modules/HibernateToolsViewlets

HQL Editor

http://www.hibernate.org/hib_docs/tools/viewlets/edit_and_run_hql.htm
prototyping HQL in HQL editor, see the generated SQL and
actually executing it to see if it works without coding Java

Criteria Query Editor

good for prototyping Criteria Query. Same thing as above.
http://www.hibernate.org/hib_docs/tools/viewlets/edit_and_run_criteria.htm

For HQL/JPA syntax checking and code completion

http://www.hibernate.org/hib_docs/tools/viewlets/java_hql_editing_and_validation.htm

Cenqua

Thu, 21 Jun 2007 19:19:29 +0000

How about Cenqua's tools (Fisheye, Clover, Crucible)? Though they are not open source, they are very nice.

Simunicator - prototyping

Thu, 21 Jun 2007 02:43:58 +0000

Hey, what better way to get the SDLC off to the right start. We use Simuncator to build exact prototypes to spec …not a typical drawing tool, this is for developers where you can plug in front end code (HTML, CSS, Javascript) and back end code (Beanshell, Velocity) ..all done online with a browser so quick to share via a URL, and with a free acount … http://www.simunication.com

Re: Code Comprehension Tools

Sun, 27 May 2007 21:24:42 +0000

Absolutely. StatCVS (along with it's cousin StatSVN) are mentioned in the book - they are great tools for keeping taps on how the source code base evolves over time.

Re: Code Comprehension Tools

Wed, 23 May 2007 07:21:21 +0000

While we are talking about tools to help manage and control existing applications I would like to mention StatCVS which helps you via CVS log analysis to understand which files are the most important ones because they got the most edits.
Sometimes even a simple sort for filesize is a great tool in finding monster classes.

Re: Code Comprehension Tools

Sun, 13 May 2007 09:17:06 +0000

Yes, decent, useful automatically generated technical reference documentation is invaluable for maintenance work. Thanks for the tip on DOxygen - I'm working on the SchemaSpy chapter at the moment, and DOxygen seems to take a similar approach, but for Java code. I may well include some material on this tool in the book.

JFS.

Code Comprehension Tools

Wed, 09 May 2007 03:33:24 +0000

The focus in this book appears to be "green field" or new projects - which is great.
Eventually a project releases and membership changes as people move on and are replaced by new members. I've found the following tools useful when arriving at a new project or job.

Doxygen: Doxygen home page a free, open source, code cross referencer that has added diagramming tools to depict relationships between modules
Understand for Java:Understand product page not free (about $495) but easier to use than Doxygen. Also supports C/C++. I really like the support provided for observing a project from a global graphical level and then drilling into code and exploring relationships. It's great for doing impact analysis of refactoring and changes.

My preferred tools

Mon, 23 Apr 2007 14:07:50 +0000

The tools I use everyday:

el4ant for build (http://el4ant.sourceforge.net), based on ant but easier to use (I find)
JUnit, DBUnit, abbot (for Swing GUI testing, sorry no web here…)
Checkstyle (+CheckClipse)
Eclipse 3.2 + UltraEdit (I don't always launch Eclipse)
EMMA
Jetty (for launching server during automatic acceptance testing), much faster than tomcat
Subversion (+ TortoiseSVN)
Derby (for DB and acceptance testing)

So far, I am plainly satisfied with all those tools.
I hope to soon set up and use the following tools:

CruiseControl
profiler4j (I currently use JMP but am not fully satisfied with it)

The Fractal Class Composition

Fri, 20 Apr 2007 10:36:55 +0000

Hmm, well The Fractal Class Composition is a design technique, but it is backed-up by a Java static code analyser: Fractality. I'm not sure whether you're particularly interested in dependency management strategies like this, though; most shops concentrate on mavenesque build and deployment dependency strategies rather than design-level dependencies.

See:
http://www.edmundkirwan.com/fracdoc/frac-page10.html

Re: Testing javascript with Firebug

Sat, 31 Mar 2007 19:27:36 +0000

Thanks, I'll check it out.