Projects

jzentest

Continuous testing framework for java. The concept is to run junit tests continuously.

maven-spring-seminar

Introducción IntroducciónEste seminario pretende ser una breve introducción práctica al uso de Spring y Maven. Para ello se desarrollará un pequeño proyecto (gestión de una biblioteca) donde se apliquen estas dos tecnologías, teniendo en cuenta de que el tipo de proyecto es multientorno ... [More] (desarrollo, integración y producción) y multimódulo (módulo de acceso a datos, módulo de servicios, modulo web de acceso a los servicios y cliente standalone de acceso a los servicios). El desarrollo de este proyecto seguirán las siguientes Normas de desarrollo. El seminario comenzará con una pequeña introducción a maven y a continuación una breve introducción a Spring. Ver el Temario del seminario [Less]

tisugly-for-java

TisUgly was developed to allow teams put their module design decisions into the build process. If particular packages access other packages or modules that are off limits based on team design decisions then the build should break. TisUgly enables teams to write their design decisions about packages ... [More] and modules into xUnit test cases to run with rest of your programmer test execution. To get started using TisUgly, please go to the Downloads area to get the library and the TisUgly wiki page for code examples. The TisUgly library is currently at version 1.0 under the Apache Software License version 2.0. More information about the Apache Software License version 2.0 can be found at: http://www.apache.org/licenses/LICENSE-2.0 Upcoming features for 2.0 release of TisUgly are: Design assertions tailored for including libraries (external jars) Negative design assertions such as "only this package can access this module" Class-level design assertions Jar-focused design assertions Regular expressions in design assertions Please feel free to send email for feature requests to to chris dot sterling at gmail dot com. [Less]

nopengine

create a tool to build the none-obvious profile for the on a community registered user.

eclipse-all-junit

A plugin to run all unit tests currently open in the workspace

moxiemocks

Moxie is a library for creating mock objects in Java. It aims to have the "nicest" syntax of any Java mocking library: Concise - set up any expectation in one Java statement. Short method names, no anonymous inner classes, no need to "replay" mock objects. Refactorable - ... [More] method name/signature changes using refactoring tools will be reflected in your tests. Easy - integrates with JUnit 4 to automatically create and verify mocks on your test objects. (You can still do this manually.) Moxie was written after years of annoyance^H^H^H^H^H^H^H^H^Hexperience with JMock, EasyMock and Mockito, and aims to take lessons form each. [Less]

Mockrunner

Mockrunner is a lightweight framework for unit testing applications in the J2EE environment. It supports servlets, filters, tag classes and Struts actions and forms. Furthermore it includes a JDBC, a JMS and a JCA test framework and can be used in conjunction with MockEJB to test EJB based ... [More] applications. Mockrunner extends JUnit and simulates the necessary behaviour without calling the real infrastructure. It does not need a running application server or a database. Furthermore it does not call the webcontainer or the Struts ActionServlet. It is very fast and enables the user to manipulate all involved classes and mock objects in all steps of the test. It can be used to write very sophisticated unit-tests for J2EE based applications without any overhead. Mockrunner does not support any [Less]

DbAssert

DbAssert is a set of assertion methods for jUnit tests to verify your database data. It uses non-intrusive way for writing unit tests, you don't have to extend any specific class to be able to query and test your database. Initialize DbAssert and start making assertions against your database right away.

snaptest

Snap Unit TestingSnapTest 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 "Mission Statement" of SortsTo put it simply, unit ... [More] 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]

2d-shooter

2D ShooterSummary2D Shooter is an exploration in Test First Development and Test Driven Development. It uses an old 2d shooter game written some time ago as a base project. The goals are to: have testing coverage greater than 80% use TDD for new functionality once test coverage is acceptable ... [More] journal and compare benefits and drawbacks to TDD with regard to this project [Less]