What are the various specification given to tester

What are the various specification given to tester at the beginning of testing. Or what are the specification a tester should satisfy during/at the end of testing at what point of time should a tester stop testing !!! thanks & regards trainee_tester

Specifications: Requirements, Design, Test Instructions.

There is no certain time/state of project when we can say 'we can now stop testing'. Testing can be a life time activitiy of a project.

Generally we can stop testing when all test cases are completed and no more scenarios in mind.

[QUOTE=trainee_tester;26911]What are the various specification given to tester at the beginning of testing. Or what are the specification a tester should satisfy during/at the end of testing at what point of time should a tester stop testing !!! thanks & regards trainee_tester[/QUOTE]

Hi,

Requirement document, Functional flows, Business Process flow document, Use cases are some of the documents provided to the test team before the beginning of the testing process.

Testing is considered to be completed when following criterias are met:

- Deadlines (release deadlines, testing deadlines, etc.)
- Test cases completed with maximum percentage passed
- Test budget depleted
- Coverage of code/functionality/requirements reaches a maximum threshold point
- Bug rate falls below a certain level
- Beta or alpha testing period ends

Regards,
Ganesan

What are Software Requirement Specification(SRS)
and Functional Requirement Specification(FRS)

and whats the need of both !!!

is there any other Requirement Specification designed for Software Testing!!!

Thanks & Regards
Trainee_tester!!!

Hi, following will define the srs and frs. Mostly they both are the requirement document provided for the software design, coding and testing. Other than this use cases are also provided. A software requirements specification (srs) is a complete description of the behavior of the system to be developed. It includes a set of use cases that describe the interactions that the users will have with the software. Use cases are also known as functional requirements. In addition to use cases, the srs also contains nonfunctional requirements. Non-functional requirements are requirements which impose constraints on the design or implementation, such as performance engineering requirements, quality standards, or design constraints. A functional requirements specification (frs) describes what is required to meet the users' business needs. Functional requirements specify which actions the design must provide in order to benefit the system's users. Functional requirements are determined by the needs, user, and task analysis of the current system. Regards, ganesan