Projects tagged ‘junit’ and ‘unittesting’

A JUnit extension that helps you to reuse fixtures and to pinpoint failures. Extends JUnit with depedencies between tests.

Great ! - You're into Extreme Programming. You've written the tests ( JUnit of course). You've done the most simple thing that could possibly work. You've even shared your keyboard with a colleague. ... [More] But have you done enough? 'Test everything that could possibly break' is the motto. But how good are the tests you've written? Are they missing any part of your code? Are you testing too much? Is something being tested only via 5 or 6 nested calls? NoUnit answers these questions by giving you a simple picture of your code. Like a Graph , NoUnit shows you a picture of your code , and reveals how good your JUnit tests are. [Less]

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

PLUTOAs in-database languages become increasingly powerful, programmers are beginning to create more and more code that runs within database management systems. Included in this mix is one of the ... [More] most popular database management systems in use today, Oracle, along with its proprietary programming language, PL/SQL. Though there many powerful tools for creating PL/SQL code, there are limited tools and frameworks for properly testing that code. The PL/SQL Unit Testing for Oracle framework, PLUTO, is the open source, object oriented, xUnit-based system for developing unit tests that attempts to fill the gap in Oracle unit testing. The framework is written in PL/SQL and is based on the Oracle object system. The inner-workings of the system are based largely on the JUnit design, with a few PL/SQL'isms added in. The system is built to be easily extended and has hooks to interface with common test runners like Perl's Test::Harness. PLUTO is lightweight, easy to install, and is free and open for everyone to use. Please feel free to give it a spin and comment back with any feedback that you might have. Interested in learning more, check out the project wiki. [Less]

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]

SpecJUnit is a Behavior Driven Test framework extension for JUnit Its actual release 1.1 counts with two flavours of test: - Description (DescriptionRunner) - Spec (SpecJUnitRunner) See some ... [More] examples: When it comes down to the actual development of test assertions, it's only necessary to give each definition and implementation of Should, see an example: [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]

JUnitBenchJUnitBench is a set of JUnit 4.x extensions for popular benchmarking and performance testing frameworks such as Japex and JMeter.

What Is App Engine Unit?App Engine Unit is a unit test harness for Google App Engine Java that is designed to let you run existing test suites in production. How Does It Work?At first glance, App ... [More] Engine and unit tests aren't a great fit. App Engine requests can only be driven by http or xmpp. Unit tests are typically initiated via command-line or IDE. App Engine requests are limited to 30 seconds. A unit test suite may contain thousands of tests that take far longer than 30 seconds to execute. How do we bridge the gap? We bridge it with App Engine Unit. App Engine Unit splits your existing test suite into small pieces and then hands off each piece to the Task Queue for asynchronous execution. How Do I Use It?You only need to do a few things to run your tests with App Engine Unit: Create a standard GAE/J web-app with all your production code, test code, production code dependencies (jars), and test code dependencies (jars) available. Create a TestRunnerConfig implementation around your test suite. Here's a JUnit3 example: package com.example; public class MyFirstTestRunnerConfig extends JUnit3Config { public TestRun newTestRun() { return new JUnit3TestRun(MyTestSuite.suite()); } }Add the following to your web.xml: App Engine Unit Test Harness App Engine Unit Test Harness TestHarness com.sortedunderbelly.appengineunit.TestHarnessServlet testharness.config.class com.example.MyFirstTestRunnerConfig TestHarness /testharness/* You might also want to lock down the test harness urls so that they are only accessible to admins: /testharness/* admin Kick off a test run by hitting http:///testharness/new Play around with installing an EmailTestRunListener, an XMPPTestRunListener, or both (via CompoundTestRunListener) in order to receive notification when your test run is finished. What's The Status Of This Project?Very early alpha. So early, in fact, that I do not yet tests. Tests are up next though. The UI is an abomination, but it's a useful abomination. All these warnings aside, it does work pretty well for non-datastore tests. LimitationsThe harness is designed to support any test framework that can run on the JVM. Currently only JUnit 3 and 4 are supported but additional frameworks can be added by providing implementations of TestHarness, TestRun, and TestHarnessConfig. Dynamically generated tests are not supported (sorry cglib wizards) Tests that belong to non-static inner class and anonymous inner classes are not supported. Support for tests that access the App Engine Datastore are a work in progress. Expect updates on this soon because it's a major pain point for me. This sounds cool, can I contribute?Yes, jump on in: http://code.google.com/p/appengineunit/issues/list Can I kick it?Yes you can. [Less]

Framework to test and mock pl/sql on Java.