Test Estimation -UAT process

Devide into tasks and estimate how much each task will take
Based on Duration, dependencies and Resources
Based on experince in past
based on size and complexity of project


UAT:Developers code software based on requirements document which is their "own" understanding of the requirements and may not actually be what the client needs from the software.

2) Requirements changes during the course of the project may not be communicated effectively to the developers

entry criteria:

• Unit Testing, Integration Testing  & System Testing  should be completed
• No Showstoppers, High, Medium defects in System Integration Test Phase 
• Regression Testing should be completed with no major defects
• All the reported defects should be fixed and tested before UAT
• Traceability matrix for all testing should be completed

Qa activity:

• Analysis of Business Requirements
• Creation of UAT test plan
• Identify Test Scenarios
• Create UAT Test Cases
• Preparation of Test Data(Production like Data)
• Run the Test cases
• Record the Results
• Confirm business objectives

Best to do:

• Prepare UAT plan early in the  project life cycle
• Conduct Pre-UAT session during System Testing phase itself
• Conduct Feedback session and  meeting before moving to production
• Beta version of the software is released to a limited number of end-users of the product to obtain feedback on the product quality

UAT tools: Fitnesse tool , WATIR