Software Testing Tools Blog – Testertools

Description:

Defect Tracker is a web-based development solution.  It tracks and organizes defect reports throughout the development cycles.  Its flexible customization enables you to adapt to your engineering changes.

Features Overview

* Engineer’s inbox (shows all defects assigned to you)
* Performing searches
* Creating public and personal reports
* Creating simple and easy to use charting in seconds
* Saving your personal and public charts
* Subscribing to defect updates by email notification
* Viewing defect change history
* Time-based escalation of defect priority
* Automatic defect assignment routing
* User management by role
* Finding out all logged on users in the system

Easy Customization Interface

You can customize the Defect Tracker without writing code.  Just use point and click, you can add, remove and modify any attribute of an object to meet your development specifications.

Database Requirement

Defect Tracker 1000 does not require a database and yet with full functional features.  If you choose to use a database later, you can simply migrate to Defect Tracker 2000.  By using the one-click data migration utility, you can migrate all your previous data into your new database.

Install and Run

All in one installation, there is nothing else to install.  You can use the Defect Tracker right away after you installed it.  There is no complicated setup and configuration.  Clients can be connected to server using a browser.  No client installation is required. Client is fully HTML based, therefore no plugins to download.

System Requirements

* HTML client runs on lastest Firefox and Internet Explorer.
* New Fire Server runs on major Java 2 platforms (currently certified on Windows and Linux, also known to run on other major platforms with java support).
* Series 1000 does not require database. Series 2000 supports the following major databases: Oracle, Microsoft SQL Server, Sybase, IBM DB2, MySQL and Informix, PostgreSQL.
* Server memory: 64 MB (Series 1000), 128 MB (Series 2000)
* Diskspace: > 100 MB
* i386 compatable processor speed for server: 500 MHz or above

View TesterTools dedicated page for this tool.

GCT was my third coverage tool.  It instruments C code in a source-to-source translation, then passes the instrumented code to a compiler.  Its first major use was on a Unix kernel, so it is suitable for measuring the coverage of embedded systems.

In addition to branch and multiple-condition coverage, it also has boundary-condition and loop coverage.  I find those useful and inexpensive types of coverage, and I’m disappointed that more coverage tools don’t include them.

It also contains a type of coverage we used for evaluating stress testing of a multiprocessor kernel.

However: GCC was written in 1992 using the GNU C compiler (gcc) as a base.  For reasons too boring to explain, it still has most of the original GCC code in it.   The practical effect of that is that porting GCT is not as trivial as it should be. Although there are Linux and Solaris ports, I do not have appropriate configuration files for them.  (If you do, please send them to me.)  There are no ports to any version of Windows or other non-Unix operating systems.  I would be stunned to see one.

Since GCT is based on gcc 1.x, it does not handle some gcc 2.x constructs.  There has been a mostly-completed port from gcc 1.x to 2.x, but I have not used it myself.

GCC has no GUI for looking at coverage results.  The output is formatted like error messages from a compiler.  It comes with an Emacs mode (based on M-x next-error) that I rather liked.  But non-Emacs users are left out in the cold – as they are in so many things.

View TesterTools dedicated page for this tool.

Security Software Testing Suite (SSTS) is a set of tools used for testing Windows security software that implement application-based security – i.e. most of the Internet security suites, HIPS, personal firewalls, behavior blockers etc.

SSTS is based on the idea of independent programs that attempt to bypass various features of the security software. Each test of SSTS is directed against a single feature or against a few closely connected features of the security software.

SSTS is used in our Proactive Security Challenge project, which goal is to rate and compare abilities of security software for Windows.  SSTS is published with its source code, which makes the testing as transparent as possible.  The suite contains many kinds of tests like outbound protection tests, self-defense tests, keylogger tests etc.  The tests in SSTS have a unified structure and user interface, hence using it is fast, easy and efficient.

View TesterTools dedicated page for this tool.

CLOC counts blank lines, comment lines, and physical lines of source code in many programming languages.  It is written entirely in Perl with no dependencies outside the standard distribution of Perl v5.6 and higher (code from some external modules is embedded within cloc) and so is quite portable.   CLOC is known to run on many flavors of Linux, Mac OS X, AIX, Solaris, IRIX, z/OS, and Windows.  (To run the Perl source version of cloc on Windows one needs ActiveState Perl 5.6.1 or higher, or Cygwin installed.  Alternatively one can use the Windows binary of cloc generated with perl2exe to run on Windows computers that have neither Perl nor Cygwin.) cloc contains code from David Wheeler’s SLOCCount, Damian Conway and Abigail’s Perl module Regexp::Common, and Sean M. Burke’s Perl module Win32::Autoglob,

cloc has many features that make it easy to use, thorough, extensible, and portable:

1. Exists as a single, self-contained file that requires minimal installation effort—just download the file and run it.

2. Can read language comment definitions from a file and thus potentially work with computer languages that do not yet exist.

3. Allows results from multiple runs to be summed together by language and y project.

4. Can produce results in a variety of formats: plain text, XML, YAML, comma separated values.

5. Can count code within compressed archives (tar balls, Zip files, Java .ear files).

6. Has numerous troubleshooting options.

7. Handles file and directory names with spaces and other unusual characters.

8. Has no dependencies outside the standard Perl distribution.

9. Runs on Linux, FreeBSD, NetBSD, Mac OS X, AIX, HP-UX, Solaris, IRIX, and z/OS systems that have Perl 5.6 or higher.  The source version runs on Windows with either ActiveState Perl or cygwin.  Alternatively on Windows one can run the Windows binary which has no dependencies.

View TesterTools dedicated page for this tool.

VectorCAST/Cover allows you to gauge the effectiveness of your test efforts by identifying which areas of an application were exercised during a test run. VectorCAST/Cover provides a convenient way to analyze the completeness of your system tests, ensuring that applications are not released with untested code. VectorCAST/Cover allows you to analyze any portion of your application, or the entire application at once. For each file that is analyzed, VectorCAST/Cover creates a multi-tabbed source-viewer widget containing the following information:

Coverage Summary – provides a color-coded view of your source code that identifies code that is completely covered, partially covered, or uncovered.

Metrics Summary – provides a tabular list of code complexity and currently achieved source-code coverage for each subprogram.

Basis Path Analysis – shows all basis paths for each subprogram.

VectorCAST/Cover Product Summary

* Identifies Tested and Untested Source
* Supports Statement, Branch, and MC/DC Coverage Reporting
* Supports Structural Coverage Levels A, B, and C for DO-178B
* Shows Aggregate Coverage Across any Subset of Test Cases
* Includes Code Complexity Metrics
* Supports Windows, Unix and Linux Platforms
* Supports Development, Integration, and System Testing
* Computes Basis Path Information for Test Case Building
* Supports Ada83/95, C, C++
* Compiler and RTOS independent

View TesterTools dedicated page for this tool.

WatirCraft is a testing framework that builds on Watir. It allows tests to be expressed as Rspec or Cucumber tests and provides a library structure to support maintainable testing. It gives you a place to put things.

Features

* Generates a directory structure for your test suite with one command.
* Provides page adapters you can customize for your application.
* Configure environment URLs and browser type (IE, Firefox) in one location.
* Supports multiple environments; specify which to test at run time.
* Uses templates to create tests and libraries.
* Automatically initializes browser for testing.
* Provides the glue to ensure your tests can find your libraries. Don’t write     another “require” statement again.
* Runs on Windows, Mac or Linux.

View TesterTools dedicated page for this tool.