Projects tagged ‘junit’ and ‘unit’

DbUnit is a JUnit extension (also usable with Ant) targeted for database-driven projects that, among other things, puts your database into a known state between test runs. This is an excellent way to ... [More] avoid the myriad of problems that can occur when one test case corrupts the database and causes subsequent tests to fail or exacerbate the damage. DbUnit has the ability to export and import your database data to and from XML datasets. Since version 2.0, DbUnit can works with very large dataset when use in streaming mode. DbUnit can also helps you to verify that your database data match expected set of values. [Less]

FEST is a collection of compact and fluent APIs, which mission is to simplify software testing. The project provides libraries for: * Functional testing of Swing-based UIs * Functional ... [More] testing of JavaFX-based UIs * Fluent interface for assertions * Easy-to-use fluent interface for Java Reflection * Template for simplifying usage of mock objects [Less]

Provides method stubbing for concrete Java classes, intended for use with JUnit 4.

daounit ease of DAO testing

Snap Unit TestingSnapTest is a powerful unit testing framework for PHP 5+, leveraging PHP's unique runtime language to simplify the unit test process without sacrificing the agility tests provide. ... [More] SnapTest is a free software project licensed under the new BSD License. SnapTest FeaturesJUnit Compliant Test Harness TAP Compliant Test Output Runnable from Command Line via .sh or .php scripts Full support for mock objects at runtime (minimum parallel structures) as actors and critics Extensible addon system for adapting SnapTest to just about any developer environment SnapTest RequirementsPHP 5.0.0+ (tested 5.1.5+ Debian, 5.2.3+ OSX) PHP binary in user path, /usr/local/bin, /opt/usr/local/bin, or in known location Basic familiarity with unit testing concepts Getting SnapTestThe latest released version is 1.2.0 Final released August 30, 2008. Bleeding edge versions can be obtained via the following repositories and methods: Git Repository: git://github.com/Jakobo/snaptest.git A browseable version of the history is available at http://github.com/Jakobo/snaptest Note: The Git Repository will always be more bleeding edge than releases. This is because the project runs primarily on the git version control system. As more distributed branches are available, they will be listed above. "Mission Statement" of SortsTo put it simply, unit testing should be transparent. There shouldn't be the complexity of test harnesses and coding out stub files. This functionality should be there if you want it, but the barrier to writing tests should be so low that it becomes easier to write the test than the code itself. It is on this philosophy that SnapTest was built. These are some of the goals of SnapTest and the SnapTest project (or at least a concept of what we are trying to do here) in no particular order: Build a PHP unit testing framework Create a 0-effort harness. Easy to run the code, easy to get results Maintain transparency in the code and the community Be as non-intrusive as possible Be memory efficient Link to complex infrastructures easily Take advantage of the OO structure PHP 5 provides Emphasize end-users as one of the most important resources Promote unit testing in a non-oo PHP world Code quickly; it's a snap. [Less]

This project provides an extension to the JUNIT framework. Following are the salient features of the project: Provide configurable inputs Run tests by selecting test suites configured in a template ... [More] file Swing based UI to select template file and run the tests Ability to rerun failed test cases Reporting of results (Includes Informational/Error results) [Less]

J2me unit testingWhen using j2meunit, one has to manually enumerate and call the tests from inside the TestCase, as well as manually call all the TestCases from within a TestSuite. This is not only ... [More] tedious but one can also easily forget to add a test or make a mistake in the test name that can result in tests not being called. This tool generates a class that calls all test methods from all test cases in the project. This is completely automatic and is meant to be part of the build of the test midlet. This project aims to make unit testing for mobile devices as easy and robust as unit testing for the desktop. J2meunit generatorThe tool scans the given directory for all unit tests and generates a test suite that executes all the tests. The typical use is for the J2ME platform where there is no reflection support and without this tool one would have to enumerate all unit tests manually. Please take a look at the Example and don't hesitate to contact me in case of any questions or suggestions. Wojciech Mlynarczyk Using mavenAdd the following plugin to your pom file: ... com.googlecode.wmlynar j2meunit-generator-maven-plugin generate generate-sources com.googlecode.wmlynar.j2meunitgenerator.example.AllTests ${basedir}/src/main/java ${basedir}/src/main/java where testsDirectory is directory containing all the tests for example /src/testme/java, targetDirectory is the directory where the generated source code will reside for example also /src/testme/java, and the className is the name of the generated class for example pl.wmlynar.tests.AllTests Additional test suites can be generated by adding further testSuite blocks. Also add the plugin repository to the pom file: j2me-unit-testing http://j2me-unit-testing.googlecode.com/svn/mavenrepo Using the tool from the command lineThe tool can also be called from command line: java -jar j2meunit-generator-1.0-bin.jar --testsDir sdir --outputDir odir --generatedClassName namewhere similarly to maven plugin: sdir is directory containing all the tests for example /src/testme/java, odir is the directory where the generated source code should reside for example also /src/testme/java, and the name is the name of the generated class for example pl.wmlynar.tests.AllTests and the tool will generate a file /src/testme/java/pl/wmlynar/tests/AllTests.javaCalling from antJust use java ant task, for example: ExampleYou can take a look at the example provided with the source code. In order to compile the example you have to set the WTK_HOME environment variable pointing to the sun wireless toolkit. In my case it is: set WTK_HOME=c:\WTK2.5.2 [Less]

FlexTestNG is a TestNG implementation for Flex. There's no public release at the moment, but there should be one in a few weeks. You can view the source tree to check on the progress. More info to come.

A simple javascript unit test framework that focuses on readability and adaptability. The aim is to produce a unit test framework for javascript that operates more like the same for other languages. This project is in its infancy, so be nice...

JUnitExt is an extension of JUnit 4, which adds additional annotations and runners for @Prerequisites, @Categories and many other things. JUnitExt provides these features:     * ... [More] @Prerequisite annotation: Ignore tests based on conditions evaluated at runtime.     * @Category annotation: Filter and Sort tests based on a Category.     * Runner, to be used for @RunWith(AnnotationRunner.class).     * Provide the old UI based runners from JUnit 3.8.2 as prebuilt jar file.     * Experimental work for JDK 1.4 backward compatibility. JUnitExt is implemented in Java, based on JDK 5, annotations etc. The implementation has been done as part of an article about JUnit 4, and has been be made public to OpenSource community. [Less]