Menu

Tree [r35] /
 History

HTTPS access


File Date Author Commit
 build_output 2006-11-25 nashjain [r3] After running the first build
 dist 2006-12-31 nashjain [r33] Made some changes and release new Zip files on ...
 docs 2006-12-31 nashjain [r34] Updated the installation video for the latest r...
 fitnesse 2006-12-11 nashjain [r24] Added Sample JUnit Test
 lib 2006-12-30 nashjain [r29] Added xerces.jar to make this work with JDK 1.5
 plugins 2006-12-31 nashjain [r31] Added eclipse/configuration folder to the clean...
 product 2006-11-26 nashjain [r9] Added the new test plugin. org.eclipse.swt.exam...
 .project 2006-11-25 nashjain [r1]
 ChangeLog.txt 2006-11-28 nashjain [r19] Added ReleaseNotes.txt and ChangeLog.txt
 LattuInstallGuide.txt 2006-12-31 nashjain [r33] Made some changes and release new Zip files on ...
 ReleaseNotes.txt 2006-12-11 nashjain [r21] Changed complete-lattu-1.0.00.beta1.zip to latt...
 build.properties 2007-01-07 nashjain [r35] Removed the different cobertura.ser files.
 build.xml 2007-01-07 nashjain [r35] Removed the different cobertura.ser files.
 build_plugin.xml 2007-01-07 nashjain [r35] Removed the different cobertura.ser files.
 readme.txt 2006-12-11 nashjain [r20]

Read Me

****************************************************************************************
*                                                                                      *
*                                   L A T T U                                          *
*                                                                                      *
****************************************************************************************

Framework for testing Eclipse RCP Applications. It can run both Unit and Functional tests. 
Essentially, it is an Eclipse Plug-in which provides Fitnesse extension to run unit and acceptance 
tests. It uses JUnit for unit testing, fitnesse for functional acceptance tests and Abbot for 
UI tests.

Why another framework?
When I started building eclipse RCP applications, there was no decent way to run my JUnit tests
from an ant build. There were some frameworks available out there, but all they gave back after 
a test run was some weird numbers to signify the test results. Clearly we needed a better way to 
run our tests and publish its results.

Also there were no acceptance testing tools available for specifying business rules for RCP 
applications. Since we were using Fitnesse for other acceptance tests, we extended Fitnesse to 
run our acceptance tests.

With the power of this framework and ant we were able to completely automate our RCP build. 
We were able to build products out of our plug-ins and run JUnit tests against them. Next we 
needed some framework to run some sample UI tests, to make sure the UI does come up after a build.

We extended the same framework by using Abbot's SWT port under the covers to perform our UI tests.

What we ended up with was a framework to run JUnit and Acceptance tests (both UI and non-UI based).

There is a lot of work left. This is only a beginning.
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.