Search Results for "mchange-commons-java" - Page 40

The goal of this project is to provide a common deployment area for all of the various Fit Servers and user-developed Fixtures.

Bug Tracker Tool written in Java EE. Friendly user interface, management of bugs, dynamic bug states, multiple users, user groups and projects.

Enterprise JUnit Beans 3 is a JUnit extension framework that allows regular JUnit tests to test Entities and Session Beans from the EJB 3.0 spec with Dependency Injection for the test classes and running on standalone EJB3 containers.

Tool for generete testcasesPresents a proposal to employ use cases to estimate the test effort and to create a finite state machine for model-based test case generation.

The easy path to Fitnesse.

Converting Fit tests automatically to JUnit tests while running. Simply add to your test suite: suite.addTest(FitlessTestStarterSuite.suiteFit("fit/html/input", "fit/output")); You do not need Fitnesse, because your fit tests run in JUnit directly.

JUnit 4 extension to perform a performance and scalability tests in a easy-to-use way using annotations

A web app that can route, record and mock web service calls. Designed for testing systems that depend on web services that are intermittent. Especially ideal for continuous integration testing.

A suite of tools that allow paralell running of unit tests under junit 4.x series. Abandoned project, because these features have been added to junit as of 4.6

This project has been relocated at http://code.google.com/p/recipientexceptions/

M3Actions is a framework to define operational semantics in MOF metamodels. It provides a graphical action language to define model behaviour, a simulator, debugger and execution trace recorder, build on top of eclipse modeling projects (EMP).

RCPATS is a toolkit to support writing of Perl scripts to exercise GUIs constructed on the Eclipse RCP using SWT.

InPUT offers a descriptive and programming language independent format and IoC (Inversion of Control) container for the configuration and design of computer experiments. Code and more info can be found on github: http://github.com/feldob/InPUT

A toolbox for testing SQL. Currently, SQL Spelunk includes code coverage analysis and calling stored procedures in a rolled-back transaction from SQL and JUnit.

OWLAND is an automated testing framework for description logic reasoners. It supports both ABox and TBox reasoning methods and is capable of running fully automated tests with any ontology and number of currently available reasoners.

These tools assist testers by generating, loading and capturing test data. Enterprise data sources are supported, including relational databases and LDAP, but are easily customized to support other data sources.

Development of traces for VDM. A trace statement is used to enhance a VDM models quality by providing an easy way to describe statements used to perform regression testing on the model. This project is related to the OvertureTool project.

This is a academic purpose software for students implement a Shop basic software at FAGOC, Brazil - MG.

Cornucopia generates testdata for SQL databases.

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).

Full Glassbox Testing Suite will improve the power of JUnit by allowing users to check if their features are following their required flow. The idea is similar to jMock but relying on real objects instead.

iTTCP means "integrated TTCP". The project integrates the TTCP compiler into Eclipse environment and allows so developing and running testcases, specified in TTCN-3 language.

SVNHookSuite is a collection of Subversion hooks (pre-commit). This Software checks the committed files against some rules (UTF-encoding, indent by tabs, ...). If one or more checks fall through, the complete commit will be rejected.

...Documentation and free support Cucumber usage example: https://github.com/zebrunner/carina-demo/tree/master/src/test/resources/features User guide: http://zebrunner.github.io/carina Demo project: https://github.com/zebrunner/carina-demo Code formatter We offer to use our configured Java code formatter for Eclipse. To use the same formatter in IntelliJ IDEA, you should install and configure Eclipse Code Formatter. Carina code formatter: https://github.com/qaprosoft/carina/blob/master/carina_formatter.xml Eclipse Code Formatter: https://plugins.jetbrains.com/plugin/6546-eclipse-code-formatter

Most software development will use a standard software development life cycle (SDLC). In SDLC, four phases are involved during development of any system. They are analysis, design, implement and testing. During testing phase, test cases are used in order to test the functionalities of the system developed. Test cases are generally extracted from the source codes manually. This paper presents an alternative approach to automate the process of generating the test cases by developing an eclipse...