Topic: role of a tester

The Role of the Test Designer / Tester is to design and document test cases, execute test cases, record test case results, document and track defects, and perform test coverage analysis. To fulfill this role the designer applies appropriate test analysis, test design, and coverage analysis methods as efficiently as possible while meeting the test organizations testing mandate. The objective is to obtain as much test coverage as possible with a minimum set of test cases.

Responsibilities and Deliverables

Test Case Design
A test case design is not the same thing as a test case . the design captures what the Test Designer / Tester is attempting to accomplish with one or more test cases. This can be as informal as a set of notes or a formal deliverable that describes the content of the test cases before the actual tests are implemented.

Test Cases
A test case is a sequence of steps designed to test one or more aspect of the application. At a minimum, each test case step should include: a description of the action, supporting data, and expected results. The test case deliverable can be captured using a "test case template" or by using one of the several commercial / freeware / shareware tools available.

Test Case Execution
Test case execution is the actual running or execution of a test case. This can be done manually or by automated scripts that perform the actions of the test case.

Capturing Test Results
Capturing test results is a simple itemization of the success or failure of any given step in a test case. Failure of a test case step does not necessarily mean that a defect has been found -- it simply means the application did not behave as expected within the context of the test case. There are several common reasons for a test case step to fail: invalid test design / expectations, invalid test data, or invalid application state. The tester should ensure that the failure was caused by the application not performing to specification and that can the failure can be replicated before raising a defect.

Document Defects
The tester documents any defects found during the execution of the test case. The tester captures: tester name, defect name, defect description, severity, impacted functional area, and any other information that would help in the remediation of the defect. A defect is the primary deliverable of any tester . it is what is used to communicate to the project team.

Test Coverage Analysis
The tester must determine if the testing mandate and defined testing scope have been satisfied -- then document the current state of the application. How coverage analysis is performed is dependent on the sources available to the tester. If the tester was able to map test cases to well formulated requirements then coverage analysis is a straightforward exercise. If this is not the case the tester must map test cases to functional areas of the application and determine if the coverage is "sufficient" -- this is obviously more of a "gut-check" than a true analysis.

Nowadays many tools available to manage all testing reports and from the last six months I'm using test management tool, Zephyr and also I have experience with using rational robot, e-manager etc, hope one of these tools help you tester to make his work easy and fast.

1. General Testing

More Emphasis on Usability, Navigation, Help and Time to Reach for Information Consistency of data / content if WEB farm, Clustering, mirroring is implemented in the sites Uptime and site optimization through site management tools while the site is up and running.

• Defects are less if RAD Tools are used

• Data in Terms of Per WEB Page (WEB page can be simple, Mod, Complex)

• Around 3 defects per man day of development and 2 defects per man day for Non developmental

• 15 % of Development Time for Look & Feel, Navigation Testing

• 25 % of Development Time for the Functionality, Security, Interfaces Testing