ContinuousIntegration: http://del.icio.us/popular/ContinuousIntegration
testing
License:LGPL
ContinuousIntegration
system:has:license
language:php
system:has:language
WET is a opensource web automation testing tool that drives an IE Browser directly: automated testing done using WET is equivalent to how a user would drive the web pages. Using WET, a developer can perform all the operations required for testing web applications – clicking a link, entering text in a textfield, clicking a button etc. WET allows a tester to perform various checks as a part of the testing process by using Checkpoints
Even though WET offers the convenience of recorders, it does so without compromising on the requirements of a true test automation tool – Powerful Scripting Ability. The WET Scripting Engine has been developed using Ruby, a powerful object oriented scripting language. WET is suitable for both the beginner level and advanced level test automation engineer.
An Advanced test automation engineer can directly take the full advantages of the WET Core engine. Since WET is written using Ruby, it exposes a tremendous amount of raw horse power. While WET has many built in testing abilities, a tester can also add libraries / use existing libraries to acheive just about any level of test automation. Your test automation is only gated by your ability to image.
A Beginner can directly jump into the world of test automation and start creating scripts using the WET UI. The WET UI, uses an innovative technique called Proxied UI of Testing using a simulated view. In this technique, you follow the same steps as in the manual test case, but in this case, you use a simulated browser view to perform these actions. With this technique, you get the convenience of a test script recorder, and at the same time, are able to overcome most of the inherent problems associated with test recorders
This release includes many new features which makes WET, arguably the best opensource alternative to expensive web testing tools
Few Features at a glance: Easy test development using the WET UI Excellent extensibility through powerful scripting ability Ability to plugin ruby libraries Object depot for good script maintanibility Object identification using multiple parameters. ‘Test definitions’ for robust test management Slick HTML results Integrated checkpoints support Integrated Datatable support Reliable popup handling
The latest build is at http://wet.qantom.org/downloads/wet_0.9.8_beta2_setup.exe
Full information about WET is available at http://wet.qantom.org
After getting the build, please go through the documentation / website to ensure that you have all the information required. You will find the required docs at a) http://www.wet.qantom.org – under ‘Docs’ tab and ‘Home -> Whitepapers’ tab b) Open QA Wiki / FAQ.
wet
Web
Development
test
testing
qa
ie
License:LGPL
License:BSD
The GNU/Linux Desktop Testing Project is a test automation project for testing the GNU desktop and improving it. It makes use of the Accessibility libraries to poke through the application’s user interface and automate interactions.
CxxTest is a JUnit/CppUnit/xUnit-like framework for C++ that doesn’t require RTTI, member template functions, exception handling, or any external libraries (including memory management, file/console I/O, or graphics libraries). It is distributed entirely as a set of header files which makes it extremely portable and usable.
CxxTest
License:LGPL
Debuggers
unittest
unit
unit-testing
C++
testing
Programming
Development
FindBugs is a program that looks for bugs in Java code.
FindBugs requires JRE (or JDK) 1.4.0 or later to run. However, it can analyze programs compiled for any version of Java.
The current beta version of FindBugs is 0.9.6, released on March 25, 2006.
FindBugs
Development
Java
Programming
testing
bugs
tools
License:LGPL
twill is a tool for Web application testing. twill implements a simple scripting language that can be used interactively or from scripts; this language contains commands for browsing the Web, filling out forms, and asserting various conditions.
twill can explore Web sites both interactively and via a script.
Jameleon is an automated testing framework that can be easily used by technical and non-technical users alike.
One of the main concepts behind Jameleon 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 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:
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.
STAF (Software Testing Automation Framework) is a framework designed to improve the level of reuse and automation in test cases and test environments.