5 projects tagged "Quality Assurance"

Pop	675.04
Vit	15.60

Bugzilla is the leading open-source/free software bug tracking system, with high-profile installations at mozilla.org, GNOME, Red Hat, and NASA, among others. It features a comprehensive set of fields, attachment management, inter-bug dependencies, email notification of changes, a powerful query interface, reporting, and Web, XML, email, and console interfaces. It can be managed entirely using a Web-based UI. The user UI is customizable using templates.

Pop	48.91
Vit	65.68

aspectj is an aspect-oriented extension to Java that enables the clean modularization of crosscutting concerns such as error checking and handling, synchronization, context-sensitive behavior, performance optimizations, monitoring and logging, debugging support, and multi-object protocols.

Pop	153.99
Vit	3.88

Anthill is a tool that ensures a controlled build process and promotes the sharing of knowledge within an organization. Anthill performs a checkout from the source repository of the latest version of a project before every build and tags the repository with a unique build number after every build. It supports many reposistory adapters including: CVS (Concurrent Versions System), Visual Source Safe, Perforce, PVCS, StarTeam, MKSIntegrity, and FileSystem. Anthill also automatically updates a project intranet site with artifacts from the latest build. Anthill is an extension to the Apache-Ant project and is compatible with version 1.3, 1.4, and 1.5 of Ant.

Pop	21.12
Vit	1.01

Delphi/Kylix/FreePascal were lacking a mock library. The Pascal Mock library enables the easy creation and use of Mock objects for unit testing, inspired by the various Java mock object tools. Mock objects ease unit testing by acting as replacements for classes that the object being tested must interact with.

Pop	65.71
Vit	1.42

Flawless traps exceptions and then uses git blame to send an email to the developer who wrote the buggy code. Even if a particular line of code causes thousands of exceptions, only one email will be sent. It uses git-blame to figure out which developer is responsible for a particular exception, and will only email that developer. If you set report_only_after_minimum_date, then Flawless will only report exceptions caused by code modified after report_only_after_minimum_date. You can mark certain files/functions as library code, and when an exception originates in those files/functions, the caller will be blamed for the error instead of the library code.