The following are the variety of the steps to consider:
· Obtain requirements, functional mode, and internal design specifications and various necessary documents.
· Obtain budget and schedule requirements.
· Determine project-related personnel and their responsibilities, reporting wants, required standards, and processes (such as release procedures, change procedures, etc.)
· Identify application's higher-risk aspects, set priorities, and determine scope and limitations of tests.
· Determine test approaches and classifications - unit, integration, functional, system, load, usability tests, etc.
· Determine test surroundings wants (hardware, software, communications, etc.)
· Determine test were wants (record/playback tools, coverage analyzers, test trailing, problem/bug tracking, etc.)
· Determine test input information wants
· Identify tasks, those responsible for tasks, and labor requirements
· Set schedule evaluations, timelines, milestones
· Determine input equivalence classes, boundary value analyses, error classes
· Prepare test set up document and have needed reviews/approvals
· Write test cases
· Have needed reviews/inspections/approvals of taking a look at cases
· Prepare to take a glance at surroundings and test ware, obtain needed user manuals/reference documents/configuration guides/installation guides, set up test trailing processes, set up logging and archiving processes, set up or obtain take a glance at file
· Acquire and install software releases
· Perform tests
· Estimate and report results Track problems/bugs and fixes
· Retest as needed
· Maintain and update test plans, test cases, test surroundings, and test were through life cycle
No comments:
Post a Comment