HATE is a test harness, a program that is intended to take the tedium out of testing and evaluating programs.

Some effort has been taken to ensure that HATE is totally independent of both the program being tested and the series of tests to be applied to the test program. The intention is to provide a single tool that may be used for both testing and evaluation; to encourage well-designed objective testing; and, by allowing researchers to apply the same sets of tests to their own programs, to make it easy for researchers to compare techniques on an informed basis.

The major features of HATE are:

HATE is written in a high-level scripting language and may be used unchanged on any platform that the language supports. This includes all flavours of Unix; Linux; Windows NT, 95, 3. n ; and the Macintosh.

Test scripts may be used unchanged on all platforms.

Test scripts are independent of the software being tested or evaluated.

Programs are interfaced to HATE by means of a short interface procedure ; thereafter, all relevant existing test scripts may be used with them.

The decomposition into test script and interface procedure, and the portablity of HATE, encourage the sharing of scripts between developers or researchers.

HATE is able to generate its output in a range of forms, including HTML and LaTeX tables.

HATE was developed principally to aid the evaluation of computer vision algorithms . There is increasing realization within the vision research community that this type of work is essential in converting computer vision from a “black art”, with algorithms being tested on only a few images, to sound engineering practice. It is hoped that the vision community will develop test scripts that allow comprehensive comparisons of existing algorithms to be performed, and that new algorithms are subsequently compared with the existing body of results.

View TesterTools dedicated page for this tool.

PrimeCode is a Software Configuration Management tool designed to manage software changes throughout the entire software life cycle on the proprietary HP NonStop™ Guardian and OSS operating systems. Go beyond source code version management to manage the relationship between all software application components, from acquisition through development, testing and production.

Develop, Package and Deploy within the same tool in compliance with your organizations SCM policies and procedures.

PrimeCode Provides:

* automated source version management

*automated executable object version management

* integrated MAKE facility

* integral release packaging, management and distribution

* protection against deletion active software components

* automated release management and distribution

* automated protection against deletion of active software components

* automated change policy (ACP)

* enterprise software distribution (ESD)

* integration with developers’ workbench tools (CEI)

* custom report writing (CRW)

View TesterTools dedicated page for this tool.

ZapGrab is very easy to use for capturing the whole or only a part of the screen.

ZapGrab : Screen capturing for tester

You only have to press the button “Grab” (to capture), select the part of the screen you want to capture and … that’s it! you have captured part of the screen.Afterwards, you can paste (crtl+v) the screen captured in a Powerpoint presentation, in a Word document, sent it by mail or publish it.

View TesterTools dedicated page for this tool.

Lightweight Test Automation Framework is an integration testing tool, which works by scripting the web browser to perform a sequence of actions against your application’s UI – entering text and clicking links and buttons exactly as a real user would – and then checking that the expected results can be seen in the browser window.

Just in case you don’t know the difference between unit testing and integration testing:

Unit tests work against the API of a particular component in your code. Ideally, they test only that single isolated unit (hence the name), which allows them to pinpoint any problems exactly where they occur. Unit testing tools for .NET include NUnit, mbUnit, and xUnit.

Integrations tests combine multiple components. Typically, they work at the UI level to test that your JavaScript, your HTML, your controller code, your model code, and your database all work together. Integration testing tools for .NET include Selenium, Watin, and Lightweight Test Automation Framework.

View TesterTools dedicated page for this tool.

EZ-Metrix® is a source code metrics utility with a difference!
It’s like a tape measure for your software…

EZ Metrix Source Code Counter with an easy Internet-based interface, multiple language support and flexible licensing features, you will be up and running in minutes with the EZ-Metrix code counter. Measure software size from virtually all text-based languages and from any platform or operating system with the same utility. Source code metrics are stored in our internal database and may be exported for further analysis. The EZ-Metrix LOC counter supports software development estimates, productivity measurement, schedule forecasting and quality analysis (CMMI, ISO).

View TesterTools dedicated page for this tool.

Understand 2.0 is the new version of our product for source code analysis, reverse engineering, code visualization and calculating code metrics. In use by tens of thousands of users world wide, it is a sophisticated tool especially valuable for maintaining impossibly large or complex amounts of source code. Multi-million SLOC projects are common with our users. There are three editions, Engineer, Pro and Analyst, with feature sets for different types of users.

View TesterTools dedicated page for this tool.

Size is one of the most important attributes of a software product. It is not only the key indicator of software cost and time but also a base unit to derive other metrics for project status and software quality measurement. Size metric is used as an essential input for most of cost estimation models such as COCOMO, SLIM, SEER-SEM and Price-S.

Although source lines of code or SLOC is a widely accepted sizing metric, there is a lack of standard that enforces a consistency of what and how to count SLOC. Ensuring consistency across independent organizations in the rules used to count software cost code is often difficult to achieve. To that end, the USC Center for Systems and Software Engineering (CSSE) has developed and released a code counting toolset called CodeCount to support sizing software code for historical data collection and reporting purposes. This toolset is a collection of tools designed to automate the collection of source code sizing information. It implements the popular code counting standards published by the Software Engineering Institute (SEI) and adapted by COCOMO. Logical and physical SLOC are among the metrics generated by the toolset.

View TesterTools dedicated page for this tool.