Search Results for "junit files"

HTTP response stubbing, matchable on URL, header and body content patterns. Request verification, runs in unit tests, as a standalone process or as a WAR app. Configurable via a fluent Java API, JSON files and JSON over HTTP. Record/playback of stubs, fault injection, per-request conditional proxying, browser proxying for request inspection and replacement. Stateful behavior simulation and configurable response delays. Mock your APIs for fast, robust and comprehensive testing. WireMock...

J2ObjC is an open-source command-line tool from Google that translates Java source code to Objective-C for the iOS (iPhone/iPad) platform. This tool enables Java source to be part of an iOS application's build, as no editing of the generated files is necessary. The goal is to write an app's non-UI code (such as application logic and data models) in Java, which is then shared by web apps (using GWT), Android apps, and iOS apps. J2ObjC supports most Java language and runtime features required...

Read and write JSON data from and to files or streams. Validation by JsonSchema (see http://json-schema.org for specifications)

This is an eclipse plugin which helps code faster in spring based applications. Please go to project homepage for more information.

Feed4JUnit makes it easy to write and feed parameterized JUnit tests with data imported from files (e.g. CSV or Excel) or generated.

A tool to generate difference between JUnit reports. This tool parses the JUnit xml report files, compares them and generates a HTML file containing the difference (viz., cases failed in new build, error cases in new build, added/deleted cases, etc).

Eclipse update site: http://master.dl.sourceforge.net/project/catsgenerationquickfixes/eclipse Please install from the eclipse update site. Provides quickfixes in eclipse for runtime errors found using EvoSuite. When a file is saved, it runs through EvoSuite which generates JUnit tests for the file. Any system failures are displayed to the user along with quickfixes that may fix the problem. The JUnit tests generated by EvoSuite can be located in the current project under /evosuite...

... index command assumes there is no duplicate data in the table column on which the index is defined). The tables' metadata are stored in .xml files, and the row data is stored in .bin files. Test cases and code are provided. This project uses JUnit 4 (only for test cases) and SAXReader (for parsing .xml). A description of the available commands is provided in "commandSyntax.txt".

A simple, easy to extend, parameter driven and customisable Java application that creates and plays Midi music files. A music notation file needs to be created. The application parses the music notation file and creates a Midi file. The application can play any Midi file. The application can read a Midi file and create an XML file from a Midi file. The application can create a music notation file from the XML file. The application includes a simple Gui interface which allows parameters...

ILEUnit is a testing framework similar to JUnit. It supports all ILE enabled languages on IBM i. It supports different output formats like spooled files, userspaces, XML stream files and integration in continuous integration server.

MTest(pymtest) is a model based testing framework written by python, which model scenarios by python scripts and then generate test cases and its descriptions to other languages, such as junit test code, c# test code, python test code, jmeter test scripts etc. It can be extended to generate tests by any lanuage when a model viewer is supplied. See https://sourceforge.net/projects/pymtest/files/MTest/

Some add-ons for junit which may never made into the official release. In short, things that work for me, may work for you, and may as well be violating the spirit of JUnit and/or unit tests.

A small, simple JDBC helper library to aid in serialising/deserialising Java objects between a database.

An Eclipse Plugin that Generates Unit Tests. Generates basic tests or Open POJO tests for simple objects and generates test stubs for complex objects. Helps developers test projects created without Unit tests or without Agile methodologies

Its purpose is to help the programmer in generating the test cases for each java file and creating controllers including junior controllers and senior controller in project.

JUCA stands for "JUnit Coverage Analyzer". It is a tool which performs a static analysis of your java class files and determines which methods of your classes are (potentially) called from JUnit testcases. The results are summarized in a HTML repor

Jutty is a code generator that will produce basic classes for a variety of patterns and standard coding classes. I'm hoping to make this an Eclipse plugin in order to start all types of new files.

A generic system test framework utilizing Spring and Junit. Specialized Junit TestCases use Spring context configuration files to define test actions and action validators, allowing the TestCase to function as an integration / system test.

TestGen4J is an open-source, automaticJava test generator that creates standard JUnit test cases from Java class or source files. In addition to reducing manual testing, it provides a data driven test harness with an automatic failed test case utility.

XML-based fixture management system for JUnit/Java. Includes JUnit extensions for automating fixture setup/destroy based on an XML description. Supports files, URL'S, SpringFramework Beans, JAR's, and Groovy scripting (future).

Goal of the project is to provide a JavaDoc doclet that transforms JUnit report XML files together with the JUnit TestCases into a HTML report that contains the JavaDoc of the TestCase and the result from the XML report file.

CxxTestNg is a JUnit/CppUnit/xUnit-like framework for C/C++. It does not require RTTI, exception handling, or any external libraries. It is only a set of header files (and a python script) that are easy to integrate into an existing project.

Log4JUnit aims to help the testing (using JUnit assertions and test cases) of legacy code that gives a train on the log files it creates, and is, appart from that not very testable (due to missing sources, not testable design, etc).