Open Source BSD Software Testing Tools

Performs basic checks on shell scripts for the presence of non portable syntax.

VaMoLa Validator is a tool to validate accessibility according to Italian Law - based on AChecker

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.

This is a simple, modular PHP class designed to record execution time benchmarks throughout different parts of a script. Compatible with virtually any PHP script, the code can be added/removed quickly and with ease. Accurate to the microsecond.

Runtime concurrency analysis for Java. Instruments your Java app at run time, and monitors field access, synchronization and locking, to verify concurrent access is safe.

Justus is a tool set for Progress 4GL (ABL) Developers. It includes a simplified parser for 4GL, an API to load Profiler data and a Test Coverage Tool.

R Unit test framework R functions implementing a standard Unit Testing framework, with additional code inspection and report generation tools

A Unibasic Code Coverage tool. It produces formatted HTML reports on the statement coverage of selected source files. Designed for UniData but should is being ported to UniVerse (still in development, but compiles and works on demonstration programs).

XJML 1.0 actually can reads one Java class and its contract (written in XML) and then executes the next verification techniques: 1. Runtime Assertion Checking (RAC). Using JML4c and JML4rt tools. 2. Extended Static Checking (ESC). Using ESC/Java2. 3. Full Static Program Verification (FSPV). Using the Why platform (tested with Why 2.30 and Why3 0.71)

Note: this tool has moved to github, this repository is not maintained any more. See https://github.com/turdusmerula/ftrace GScopeLog is a tool for instrumenting c++ code through gcc. The main purpose is to trace entry/exit point of functions. A status file may be generated to give overview of functions calls and timing informations with minimal impact on performances.

gcRadar is not a static code anayser but it is a library using which is ment to beused in your source code and it will monitor and report the lifetime events of yuor objects. gcRadar can provide this information by using callbacks, log4j & polling. gcRadar can monitor entities ranging from individula objects to full object trees comprising of is-a & has-a relationships. By using gcRadar you can monitor the lifetime of the objects that are created by your application in runtime, gcRadar enables the application to be aware of the memory constaraints that arise at runtime. The workings of the mythical Java Garbage Collector have for long eluded the common developer. Now by gcRadar enable you to record the life and death of objects at runtime.

Its an Eclipse 3.5 Plugin. It can be used to find linear paths for unit testing of any method. The linear path covers all the child methods and till leaf level of the hierarchy. The packages which should be covered in the path can be controlled.

Recognizes typical patterns in Java code which could be replaced with functions provided by open source libraries http://www.jnorm.org

A program to check source code for mispelings...

The 'pysourceinfo' package provides source information on Python runtime objects based on 'inspect', 'sys', 'os', and 'imp'. The covered objects include packages, modules, functions, methods, scripts, and classes by two views: - File System View - packages, modules, and linenumbers - based on files and paths - Runtime Object View - callables, classes, and containers - based on in-memory RTTI / introspection The supported platforms are: - Linux, BSD, Unix, OS-X, Cygwin, and Windows - Python2, Python3 - CPython, PyPy Object addresses within modules - Object Identifier OID - and the display of the runtime call flow are supported by 'PyStackInfo'. Online documents: https://pysourceinfo.sourceforge.io/