Jameleon project is an automated testing framework that can be used by technical and non-technical users alike.
One of the main concepts behind it is to create a group of keywords or tags that represent different screens of an application. All of the logic required to automate each particular screen can be defined in Java and mapped to these keywords.
The keywords can then be organized with different data sets to form test scripts without requiring an in-depth knowledge of how the application works. The test scripts are then used to automate testing efforts and to generate manual test case documentation.
Jameleon was designed to test many kinds of applications. To make this possible, Jameleon was designed with a plug-in model. Currently, there are five plug-ins offered;
· A JUnit plug-in which can be used to test at a white box level. All JUnit function tags can be used in conjunction with other plug-ins.
· A Jiffie plug-in which drives Internet Explorer and can therefore only be run on Windows. Most testers like this plug-in the most.
· An HttpUnit plug-in which emulates a browser. Most developers like this plug-in the most.
· A 3270 (Jagacy) plug-in which is used to automate mainframe applications.
· A jWebUnit plug-in which is the most basic among the provided plug-ins and currently has no generic tags other than a session tag.
If Jameleon doesn't have some feature or plug-in, please feel free to request it as a feature via the Request a Feature link. Implementing Jameleon plug-ins is simple and can usually be done in less than a hour.
Even though it would be possible to write unit tests using Jameleon, Jameleon was designed with integration, regression, functional, and acceptance-level testing in mind. Most bugs are found and fixed by good unit tests. However, this does not eliminate the need to test the application as a whole.
What's New in 3.3 RC1 Development Release:
· A few results bugs regarding IE 6 and IE 7 were fixed, the results are now generated based on the desired character set, and this release runs against Java 1.4.2, 5.0, and 6.0 again.