Bugzero is a Web-based change management and issue tracking system used in a distributed team environment to track software bugs, hardware defects, test cases, or any other issues. It can also be used equally well as a helpdesk customer support, trouble ticketing, or email management system to collect and manage customer feedbacks, incidents, requests, and issues. It is easy to use, but still flexible and adaptive, and can be configured to fit to your organization's unique business process and workflow.
Ozibug is a platform-independent, Web-based bug tracking system that can be installed and run straight out of the box on any Java servlet capable platform. It can be used to manage the reporting of bugs and tracking of their progress from discovery through to resolution. It provides standard features such as file attachments, multiple module support, email notifications, custom reports, and RSS feeds. For those who require more flexibility, it also offers fine grained access control, database storage, pluggable authentication, an incoming mail gateway, and customizable appearance, email notifications, and reference data.
GNATS is a portable incident/bug report/help request-tracking system which runs on UNIX-like operating systems. It easily handles thousands of problem reports, has been in wide use since the early 90s, and can do most of its operations over e-mail. Several front end interfaces exist, including command line, emacs, and Tcl/Tk interfaces. There are also a number of Web (CGI) interfaces written in scripting languages like Perl and Python.
ReadySET is a project to produce and maintain a library of reusable software engineering document templates. These templates provide a ready starting point for the documents used in software development projects. Using good templates can help developers work more quickly, and they help prompt discussion and avoid oversights. Key features include: high-quality outlines, sample text, and checklists, use of simple Web technologies (pure XHTML and CSS), and templates for many common software engineering documents.
Parabuild is a software build and release management system. It helps software teams and organizations reduce risks of project failures by providing practically unbreakable scheduled, release builds and Continuous Integration. It supports Perforce, Subversion, CVS, Surround SCM, AccuRev, ClearCase, Serena ChangeMan (PVCS), Borland StarTeam, SourceGear Vault, Visual SourceSafe, and MKS Source Integrity.
Track+ is a fully featured Web-based issue tracking and bug tracking system build on top of J2EE and Struts and entirely written in Java. It supports many database systems such as Oracle 9i, MySQL, PostgreSQL, MS SQL Server, etc. It automatically sends email, can do user authentication via LDAP, creates comprehensive reports, and much more. It comes with online help, German, English, and Norwegian localizations, and an elaborate manual.
Testitool is a Web-based application for QA test planning. It creates a test plan and populates it with test cases, maps test cases to functional requirements, instantiates a test plan, begins executing test cases and marks them as successful or failed, generates reports on your test plans, copies test plans and test cases, and tailors test plan instances by adding and removing test cases from them.
CUT is a unit-testing framework for C, C++, and Objective-C. Unlike other unit testing tools, CUT doesn't strive to be an SUnit clone. It automates a lot of the drudge work often encountered when using other unit testing packages for the C family of programming languages. CUT may also be used to unit-test assembly language software in some circumstances.
NoBug is a library which provides assertions, logging statements, and annotations for C and C++ programs. It includes pre-/post-condition and invariant checks, as well as generic assertions. Checks are enabled based on build-levels and scope tags. It also includes debugger support (valgrind), dumping of data structures, logging your application's activities, runtime customizable logging via environment variables, different logging targets (ringbuffer, stderr, syslog, debugger, etc.), and annotation of your source code regarding known bugs, things to do, and planned things. It can track resources and detect deadlocks.