QATestingTools.com

DevTest - Complete Quality Assurance Test Management :
DevTest provides total control of every aspect of the testing process from test planning and team management to analyzing test results. DevTest helps to create and manage release and test cycles, plan and assign test tasks to the testing teams, execute test coverage, and submit product defects all from within a single application. DevTest crunches the numbers while your team is testing, providing built-in, dynamic test analysis without having to break out the spreadsheets.

Typemock Isolator is a tool that enables C# and Visual Basic developers to write unit tests in an easy, reliable, and fast manner. Typemock Isolator is tightly integrated with MS Visual Studio. You can write, run, and debug tests and see code coverage from within the MS Visual Studio user interface. In addition, Typemock Isolator provides an Application Programming Interface (API). This API helps you write simple and human readable tests which are completely isolated from the production code.

It helps to :

AgitarOne Agitator provides a unique interactive understanding of code behavior as a developer writes or modifies Java classes or methods. Agitation helps developers validate the expected behavior of their code and discover unexpected behaviors. Agitator automatically creates dynamic test cases, synthesizes sets of input data, and analyzes the results. When objects depend on other objects, Agitator automatically constructs those objects, enabling full analysis of the possible behaviors of the code, even if it depends on third-party libraries.

StoryTestIQ (STIQ) is a test framework used to create Automated Acceptance Tests or Story Tests. STIQ is a mashup of Selenium and FitNesse. It is "wiki-ized" Selenium with widgets and features that make it easier to write and organize Selenium tests. STIQ is used to record Customer needs and acceptance criteria; the tests are a big part of the "Definition of Done". The Story Tests written at the beginning of an iteration will initially fail. It is the responsibility of the team to implement the requirements in order to make the Story Tests pass. This practice is called Story Test Driven Development and it is a natural extension of the well known Test-Driven Development and Automated Acceptance Testing practices.