Projects tagged ‘junit’ and ‘testng’

FEST is a collection of libraries that aims at simplifying creation and maintenance of automated tests. Its main module, the Swing module, provides the following benefits: * Simulation of user-generated events and reliable GUI component ... [More] lookup * Easy-to-use and powerful API that simplifies creation and maintenance of Swing GUI functional tests * Supports both JUnit and TestNG * Ability to take screenshots of failed GUI tests and embed them in a HTML report (JUnit and TestNG) * Experimental Groovy Builder support for creating GUI tests [Less]

An alternative HTML reporting plug-in for TestNG. Generates easy-to-understand XHTML reports. Also includes a basic JUnit format XML reporter.

JsTester allows validation of javaScript code inside java. It provides a group of assert methods like JUnit's Assert, it also supports the validations described in http://javascript.crockford.com/remedial.html, and the ability to use your own ... [More] validations (unary & binary predicates). The project provides two ways of creating your tests: by inheritance (JsTestCase), and by composition (JsTester). Use JsTestCase as you would normally use any extension of TestCase. Use JsTester with TestNG or JUnit4 and annotations, or inside another TestCase hierarchy. Includes Groovy support. [Less]

The Umangite framework simplifies the task of writing web tests with Selenium. It's built on TestNG, Spring and Cargo. Here is an example of a simple test: public class HelloWorldTest extends AbstractSeleniumTest { @Override protected ... [More] String[] getConfigLocations() { return new String[] { ... }; } @Test public void test() { open('/testwebapp/index.html'); assertTextPresent('Hello There'); } }AbstractSeleniumTest has an @BeforeClass method that starts the web container and Selenium and @AfterClass method that shuts them down. It also injects itself with Spring beans (from an application context defined by the getConfigLocations()). The Spring beans are responsible for launching Selenium and the web container. There are currently two launchers: one that runs an embedded Jetty and the other uses Cargo to launch Tomcat (To be generalized to support other containers). Here are some example bean definitions: Once of the nice things around this framework is that the same test class can be run with multiple containers - e.g. both Jetty for nimble developer testing and Tomcat for other tests. [Less]