Search Results for "java modelling tools"

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. It brings code coverage analysis directly into the Eclipse workbench. The EclEmma project is also the home of the JaCoCo code coverage library which is the technical back-end for EclEmma and also has integrations with many other build and software quality tools.

A group of Java-based testing tools and JUnit extensions aimed at increasing quality awareness and ease of introduction of testing tools into the development cycle. Examples are Automated documentation, class hierarchy unit testing, and code coverage.

An integrated testing framework, covering test case generation, execution, bug reporting, code coverage and coding conventions. Currently This is a module suite for netbeans IDE, integrating some open source PHP Testing Tools

Unzip buildtemplate and you will have a project set up with ant/junit/verifydesign/code coverage all out of the box. It is a great way to get started and then add to the build.xml as you go. netbuildtemplate is for .net and has nant/nunit/NCover, etc.

EL4Ant is a light and efficient build system based on Apache Ant. A project is described in XML as modules with transitive dependencies. Features are provided thanks to plugins: Java execution, JUnit reports, EMMA code coverage, Eclipse integration...

EMMA is a fast Java code coverage tool based on bytecode instrumentation. It differs from the existing tools by enabling coverage profiling on large scale enterprise software projects with simultaneous emphasis on fast individual development.

gcov-eclipse is an Eclipse plug-in that will extend CDT to provide code-coverage testing to C/C++ projects by using the gcov program. It will integrate into the CDT's launch and managed build system.

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.

Measure how directly your classes are tested by JUnit. Unlike traditional code coverage tools, PEA considers and measures whether the code covered ran as a direct call from a test, or indirectly via chained calls.

JUnitMetrics is a tool that enables to measure basic JUnit and Cactus tests metrics (like number of tests, assertions, number of executed assertions). It is great, complementary solution to code coverage tools and mutation testers.