Software Testing Tools

In this post I am going to explain the different types of Software Testing Tools(Automation) with feature.

1. Funtionality Testing Tools(Capture/playback tools)

a) Capture user operations including keystrokes, mouse activity, and display output.

b) These captured tests form a baseline for future testing of product changes.

c) The tool can automatically play back previously captured tests whenever needed and validate the results by comparing them to the previously saved baseline.

Example: WinRunner, QTP, SilkTest, etc

d) This makes regression testing easier.

2. Memory testing (bounds-checkers):

Memory testing tools are software programs that perform detailed tests of your computer's memory system. Detect memory problems, exceeding array bounds, memory allocated but not freed, reading and using uninitialized memory.

The memory installed in your computer is very sensitive. It's always a good idea to test newly purchased memory for errors and a memory test is always in order if you suspect that you may have a hardware problem.

Example: Memtest86, Memtest86+, Windows Memory Diagnostic, M2K MemScope etc

3. Tools for performance testing of client/server applications:

System performance is generally assessed in terms of response time and throughput rates under differing processing and configuration conditions. Performance testing can serve different purposes. It can demonstrate that the system meets performance criteria. It can compare two systems to find which performs better. Or it can measure what parts of the system or workload cause the system to perform badly. In the diagnostic case, software engineers use tools such as profilers to measure what parts of a device or software contribute most to the poor performance or to establish throughput levels (and thresholds) for maintained acceptable response time. It is critical to the cost performance of a new system, that performance test efforts begin at the inception of the development project and extend through to deployment. The later a performance defect is detected, the higher the cost of remediation. This is true in the case of functional testing, but even more so with performance testing, due to the end-to-end nature of its scope.

Example: Load Runner, Jmeter etc

4. Test case management Tools

1. Provide a user interface for managing tests.
2. Organize tests for ease of use and maintenance
3. Start and manage test execution sessions that run user-selected tests
4. Provide seamless integration with capture/palyback and coverage analysis tools
5. Provide automated test reporting and documentation.

Example: Test Director, Quality Center etc.

5. Defect tracking tools:

1. Used to record, track, and generally assist with the management of defects
2. Submit and update defect reports
3. Generate pre-defined or user-defined management reports
4. Selectively notify users automatically of changes in defect status
5. Provide secured access to all data via user-defined queries.

Example: Bugzilla, Remedy, Bug Tracker, Request Tracker etc

6. Coverage analyzers:

1. Tell us which parts of the product under test have been executed (covered) by the current tests
2. Identifies parts not covered varieties of coverage - statement, decision, … etc.