Ravi

• Jun 1st, 2005

 

The duties of the software Tester is to go through the requirements documents and functional specification and based on those documents one should focus on writing test cases, which covers all the functionality to be tested. The tester should carry out all these procedures at the time of application under development. Once the build is ready for testing, we know what to test and how to proceed for the testing. Make sure, main functionality is tested first, so that all other testers can be ready for testing their modules/functionality.

raju

• Jun 6th, 2005

 

very good answer

kotireddy

• Jun 28th, 2005

 

answer to this question is first u understand the application, functionality,working of the application,if perticular funtionality is no need to test for perticular application that type of application u don't do test. 
these type of activities u know only if u can understand the application.....

choudary

• Jul 8th, 2005

 

study the Requirements document,design document throughly, to understand the main functionality of the application. after u get a clear idea on that then only start write test cases. 
if u have any doubts send them to the concerned person(Generally Business Analyst). 
IMP: if u have tight schedule i.e; there is no much time for testing , then test only the important functionalities. u can get the information about those important functionalities in Risk Analysis Documentaion.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 27th, 2009

 

I determine what to test in the following ways:

1) By learning as much about the product as I possibly can.

2) By asking a lot of questions and gaining insight from:
- clients
- customers
- members of the business sector
- marketing
- engineers
- software developers

3) I use any information which identifies our company's intent for the product as long as it can be verified with a true or false (pass or fail) result.  I find this information in:
- Software Requirements Specification
- Functional Requirements Document
- Business Requirements Document
- Work-flow Diagrams
- Wireframes
- Mock-ups
- Claims made in Marketing materials and brochures
- End-User License Agreement (EULA)
- Information found in Help text
- Customer Support documentation and knowledge base

4) I conduct risk-based analysis in order to determine my test priorities.  I consider:
- things that have changed
- core functionalities
- common usage
- high impact areas
- most wanted areas
 

Anup

• Jul 29th, 2013

 

First go through the BRS (business requirement specification) then takeout out the SRS (Software requirement Specification) by analyzing the requirement of the client then filter out the FRS (Functional requirement specification) then choose what to be tested first, when and write the test cases according to track the coverage of the test and activity.