Search Results for "java automation"

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.

Code Coverage Tool For Oracle PL/SQL

An eclipse plugin for code coverage visualization of JUnit Tests. Especially useful for test-first development. Supported coverages include block coverage and all-uses coverage (Data Flow Analysis).

Coberclipse is a eclipse plugin for Corbertura. It will instrument the classes during the build and show the code coverage after executing unit test cases.

Codemon is a testing tool that enables code coverage of C codes. It supports the level of Decision Coverage and Condition Coverage.

BeCover is a Java code coverage tool based on source-code analysis. The main goal is to keep it small and fast, so using it as a plugin in the common IDE's can be achieved.

This profiler (JRE 1.5.0 only) uses JVMTI and native bytecode instrumentation for the analysis of the heap, reachable objects, execution time, garbage collection efficiency, code coverage and thread contention. No preparation steps required in build.

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.

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.

Tiria is a eclipse-plugin to view code coverage data (e.g. from cobertura) within the IDE. Main objective of the plugin is to show how the code coverage changes during project progress.

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.