Friday, April 2, 2010

Meetings

Client Meetings:
Some Time client will call testing team, find the staus of testing process.If Test Scenarios are created some time you have to discuss with the client regarding the scenarios.Some time you can directly talk to client regarding schedule of release final build.

Team Meeting:
Every End of Session there will be a meeting in between team,Reagarding Test Schedules, Reagrding Bug...

Staus Meeting:
Generally Every weekend This Meeting will held,Here discussion on Testing Process, How many Bugs raised in the last week, What type of bugs raiised(critical,Low..),Proceding Steps to the comeing week..

#. Obtain requirements, functional design, and internal design specifications and other necessary documents
#. Obtain budget and schedule requirements
#. Determine project-related personnel and their responsibilities, reporting requirements, required standards and processes (such as release processes, change processes, etc.)
#. Determine project context, relative to the existing quality culture of the organization and business, and how it might impact testing scope, aproaches, and methods.
#. Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests
#. Determine test approaches and methods - unit, integration, functional, system, load, usability tests, etc.
#. Determine test environment requirements (hardware, software, communications, etc.)
#. Determine testware requirements (record/playback tools, coverage analyzers, test tracking, problem/bug tracking, etc.)
#. Determine test input data requirements
#. Identify tasks, those responsible for tasks, and labor requirements
#. Set schedule estimates, timelines, milestones
#. Determine input equivalence classes, boundary value analyses, error classes
#. Prepare test plan document and have needed reviews/approvals
#. Write test cases
#. Have needed reviews/inspections/approvals of test cases
#. Prepare test environment and testware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test tracking processes, set up logging and archiving processes, set up or obtain test input data
#. Obtain and install software releases
#. Perform tests
#. Evaluate and report results
#. Track problems/bugs and fixes
#. Retest as needed
#. Maintain and update test plans, test cases, test environment, and testware through life cycle

No comments: