Post3 d test plan wk13
Upcoming SlideShare
Loading in...5

Post3 d test plan wk13






Total Views
Slideshare-icon Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Post3 d test plan wk13 Post3 d test plan wk13 Presentation Transcript

    • Post3D Release WK13Software QA Test Plan
    • Content
      Test Items
      Feature to be tested
      Features not to be tested
      VII. Item pass/failed criteria
      VIII. Testing tasks
      IX. Environmental needs
      X. Schedule
      XI. Risk assessment
      XII. Approvals
    • I. Identifier
      Present QA TP is composed for release 3/28/11 and is a part of “Post3D” Product Plan
    • II. Introduction
      Current TP is designed to cover all required tests for items from “Post3D WK11 Release Notes”:
      and Bugs list (Brian’s spreadsheet).
      Page Flows, Page Details, Mock Screen, Use Case Details and Business Requirement can be found in the following documents:
      - Post3D Sprint 3 Detail
    • - Post3D Sprint 2 Details
      - Post3D Sprint 1 Details
      Additional info can be found on BaseCamp Post3d page:
    • III. Test Items
      The following is a list, by version and release, of the items to be tested:
      • Current build version at time of testing:
      ( 3DVIA Player build 2.10.53 Drop5, DB)
    • IV. Features to be tested
      Javascript changes(callback registration)
      Showcase User Management Features
      Web Purify
      Security Changes
      3DVIA Content Uploading
      Dashboard content and appearance
      User’s email
      “Post” Features
    • V. Features not to be tested (?)
      The following is a list of the areas that will not be specifically addressed. All testing in these areas will be indirect as a result of other testing efforts.
    • VI. Approach
      One full-time QA Specialist composes and runs all TCs. (development teams participation -?)
      - Wiki QA /Current Releases/Post3D Release WK13/Test Cases
      - Sticky notes on Scrum Board ( Todd, Iryna)
      - Bugs (Bugzilla)
      - Daily (?) progress report to Project Manager
      2. QA Acceptance into testing - ? (TBD)
      Main Activities involved into testing: UGI, System, Performance, Integration, Verification, Regression, Negative.
      2. User Acceptance Test is run by Product
      Manager (Brian) Friday
      3. QA Testing Term: 3/18 -3/27 (5 business day)
    • VII. Item Pass/Fail Criteria
      Program is considered “Pass” if main users flows worked according to the Requirements
      All new/existed issues for current release have to be fixed or moved to another milestone.(no blockers or P1 bugs, a few low priority bugs are acceptable)
      The test process will be stopped once at least 4 end-to-end user cases with run flawlessly.
    • VIII. Testing TasksList of all tasks necessary to prepare for and do testing:
      Create User Acceptance Test Plan;
      Verify prototypes of Screens and logic;
      Create Regression Test Plan;
      4. Test Data preparation(example: 3dvia files)
    • IX. Environmental Needs
      RM and VM :
      • Windows 7 SP1, Windows XP SP2 ,
      Windows XP SP3 (W510, DELL);
      • IE7, IE8, FF3.5, Chrome 10;
      • Various testing tools(XENU, Nimbus etc.)
    • X. Schedule
    • XI. Risk Assessment1. There are some parts of the project that are not within the control of our application, but have direct impact on the Product. 2. Backup and Recovery of local databases 3. Outage?
      Brian _________________________
      Todd _________________________
      Date : __________________________