Prashant

• Jun 10th, 2005

 

I would study the functional and business requirement documents. Get answers from BA and FA, if I have any questions. I would understand the functionality and figure out role and size of my module in terms of the whole application. This is the way I would understand the scope of the module and thus its testing. 
I would get data, make sure environment is up and running, ensure other pieces/services are as needed (for my module to interact), and see that testing documents are approved (test plans, test design documents, test cases, bug templates etc). 
Per test cases that are reviewd and approved by concerned person(s).

choudary

• Jul 5th, 2005

 

SCOPE: i study the BRS throughly. if i have any doubts in that i sent them to Business Analyst. he sends replies to me. like this i underdand the scope of my module. 
ORGANISE: after that i starts preparing test cases. when i completed, i send them to the test lead. the test lead will approve or reject them. if he rejects i starts again. 
EXECUTE: here i check the environment i.e; whether it is ready or not. and verify other services which are required for this module are ready or not.and see whether testing documents are approved or not.

sangeetha.k

• Aug 16th, 2005

 

Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoints meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and discuss testing issues, status and activities.

Amit

• Sep 23rd, 2005

 

studing for inteviews of software testing and trying to find answer of this question

Suman

• Oct 21st, 2005

 

How do you scope, organize, and execute a test project?

Gangadhar Nidudavolu

• Jan 6th, 2006

 

The Scope can be defined from the BRS, SRS, FRS or from functional points. It may be anything that is provided by the client.

And regarding organizing we need to analyze the functionality to be covered and who will testing the modules and pros and cons of the application.

Identify the number if test cases, resource allocation , what are the risks that we need mutigate all these come into picture.

Once this is done it is very easy to execute based on the plan what we have chalked out.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 5th, 2009

 

The answer to this question depends on your role in the test team.  The Test Manager, Test Lead, and Tester will approach the process differently.  I will answer this question as if it were posed for the Tester role.

To SCOPE the project, I would:
1) Learn as much about the application as possible by studing the Business Requirements Document (BRD), Technical Specifications, Work-Flow Diagrams, Wireframes, System Architectural Diagrams, Marketing and Legal documents, and any other relevant information that is available.
2) Request additional information from expert stakeholders internal and external to the company if necessary.
3) Estimate the amount of time it will take to create test cases and to execute them.
4) Determine how the test environment should be configured.
5) Determine whether any test tools are needed.
6) Create a Test Plan that covers test strategies, test scope, etc..
7) Request that expert stakeholders review my Test Plan and provide feedback to improve it.
8) Revise the Test Plan, including test strategies and scope, to correspond with all useful feedback I received from stakeholders.

To ORGANIZE the project, I would:
1) Break the application down into functional areas.
2) Create a test suite that includes folders for each functional area to be tested.
3) Create test cases corresponding to each functional area and place them under their proper folders.
4) Map the requirements to test cases.
5) Prioritize the test cases.
 

To EXECUTE the project, I would:
1) Ensure the test environment is ready for test.
2) Ensure the test tools are ready for test.
3) Ensure I have all supporting documentation required for testing.
4) Access my test suite and begin testing!