Regular qa activity

As soon as we get the requirements specification document I analyse the requirements give my feed back,do any clarifications if any ambiguity in req's, any missing parts etc.
once we get the design document and srs we start writing test plan with test strategy,types of tests to be carried, scope, envi, resources, schedule, risks, dependencies, exit criteria, defect tracking,tools etc..
i will give  a test plan walk through and once it is approved, we start writing test cases and prepare test scripts.

Integration testing

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

SDLC

Water fall:

Requirements gathering :Gather as much information as possible about the details & specifications of the desired software from the client

Design Stage:Plan the programming language like java , php , .net ; database like oracle , mysql etc which would be suited for the project
Built Stage: actual code
 TEST stage:Test the software to verify that it is built as per the specifications given by the client. 
Maintenance stage.:you may to do some code changes to accommodate enhancements requested by the client.
STLC:

TEst planning stage: 

• Preparation of test plan/strategy document for various types of testing
• Test tool selection 
• Test effort estimation 
• Resource planning and determining roles and responsibilities.
• Training requirement

Envi setup: 

• Setup test Environment and test data 
• Perform smoke test on the build

Test closure:

• Evaluate cycle completion criteria based on Time,Test coverage,Cost, Quality
• Prepare test metrics ,Test closure report 
• Document the learning out of the project 

Manual Testing

http://kttbase.blogspot.com/2014/09/about-me.html

http://kttbase.blogspot.com/2014/09/test-data-test-execution-test-metrics.html

http://kttbase.blogspot.com/2014/09/best-practices-process-improvement.html

http://kttbase.blogspot.com/2014/09/testplan-defect-test-case.html

http://kttbase.blogspot.com/2014/09/testplan-defect-test-case.html

http://kttbase.blogspot.com/2014/09/alm.html

http://kttbase.blogspot.com/2014/09/my-sql.html

http://kttbase.blogspot.com/2014/09/severity-and-priority.html

http://kttbase.blogspot.com/2014/09/happy-path-quality.html

http://kttbase.blogspot.com/2014/09/bread-toaster-example.html

http://kttbase.blogspot.com/2014/09/personal-qns.html