Open Source Software Testing Tools - Page 42

A language-validation testing harness for Java (and Java-like) compilers & other language tools. Provides a framework for verifying whether static/runtime errors occur when running collections of test programs (benchmarks) described by "jlbench" files.

"Java log viewer" is a GUI to easily view the java application logs generated by the "java.util.logging" package. The log must be formatted by the XMLFormatter class. It provides facilities in order to filter, to sort and to find log records.

Java Mutantion Testing for Eclipse is a plugin for Eclipse that enables mutation testing for Java projects. JMuTE introduces mutations to java source code, runs junit tests and generates an html report.

Java library to parse GNU Makefiles. The source code is available from SVN. The latest revision should be in trunk, the latest "stable" release should be in branch.

A generic java based distributed performance testing platform specifically for testing clustered or distributed applications and or frameworks. The framework itself is clustered and coordinated with www.terracotta.org

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.

This is a Java program designed for helping programmers to test text strings based on user input made Java regular expressions.

Java tool for searching classpath for resources such as class or files. Drag and drop interface for add new jars to your search path. Useful for resolving those class not found problem such as java.lang.ClassNotFoundException and java.lang.NoClassDefFoun

Stopwatch is a simple, highly extensible, API that alows monitoring of any part of the application. It reports hits, execution times and load but can be extended to do more via custom engines. It is able to persist data in "in-memory" or real database.

This project is designed to help programmers understand the resource utilization of their code in the Java Virtual Machine and provide real time feedback via a GUI interface.

The Java-Based-GUI-Test-Automation-Library (jabuta) provides the possibility to test software on a GUI-based level.

In our proposed work, we combine feedback-directed test cases generation with concolic testing to form Java-Hybrid Concolic Testing (Java-HCT). Java-HCT generates test cases combine so that, it create more number of test cases. Hence, through Java-HCT we achieve high MC/DC. Combinations of approaches represent different tradeoffs of completeness and scalability. We developed Java-HCT using RANDOOP, jCUTE, and COPECA. Combination of RANDOOP and jCUTE creates more test cases. COPECA is used to measure MC/DC\% using these generated test cases. Experimental study shows that Java-HCT produce better MC/DC\% through individual testing techniques(feedback-directed random testing and concolic testing).

A collection of software benchmarks developed to compare the performance of Java with C on identical code. No language libraries were used to avoid implementation differences. Some of the benchmarks are also implemented in Python and Scala. There are benchmarks for bit twiddling, numerical computing, data structure manipulation, concurrent computing, callouts to native libraries, and, graphics processing units (GPU) utilization.

Automated testing tool for algorithms supported by all smart card with JavaCard platform. To view all files about this project or discussion, you can visit:

This is a xUnit framework implementation for JavaFX. Basically it's a JUnit clone for JavaFX script language.

This project is a java web application developer toolbox. It is among other, a simple and powerful framework which does not require dealing with XML files. It also provides a lot of other features, such as a DB abstraction layer, a nice javadoc doclet, a

PLEASE NOTE - JAVAPATHFINDER HAS MOVED TO: http://babelfish.arc.nasa.gov/trac/jpf Java PathFinder is a system to verify executable Java bytecode programs.

Method stubbing framework for concrete classes in Java, intended for use with JUnit 4. It no longer requires jMock for mocking interfaces and classes.

jsAssertUnit is a unit testing framework based on assertions, helping JavaScript developers to test their code. Failing assertions about the program state are tracked in a Reporter window of a DOM compliant browser : IE5+, Mozilla, Netscape 6+, etc.

JdbcProxy is a JDBC 2.0 driver that can help debug or test applications. The driver can wrap another JDBC driver to debug the JDBC calls done by the application. The driver can also emulate another JDBC driver to test the application without a database.

Jdptool is a debug and profiler tool which based on JPDA; It provide both swing based and browser based GUI. It has sophisticated debugger without user interfere. It also provide profiler to memory usage and threads with numerous new feature

Jeek is a concrete class / stub / mock code generator for .NET, used in unit testing.

Most continuous integration platforms limit the number of threads one can use. If you have more than one test suite running puppeteer chances are that your test will timeout. This is because jest will try to run puppeteer in parallel and the CI platform won't be able to handle all the parallel jobs in time. A fix to this is to run your test serially when in a CI environment. Users have discovered that running test serially in such environments can render up to 50% of performance gains. Writing integration test can be done using Puppeteer API but it can be complicated and hard because API is not designed for testing. Debugging tests can be hard sometimes and it is very useful to be able to pause tests in order to inspect the browser. Jest Puppeteer exposes a method jestPuppeteer.debug() that suspends test execution and gives you the opportunity to see what's going on in the browser.

Jester.NET is a port of the popular Jester mutation testing tool for Java. Jester.NET is designed to slightly mutate your application code and then run your unit tests in order to expose gaps in your testing strategy.