The document outlines a test plan for the Post3D WK13 release, including: - Features to be tested such as JavaScript changes, user management, security changes, and content uploading - Approach of having one QA specialist run all test cases and report daily progress - Testing tasks such as creating test plans, verifying screens, and preparing test data - Pass/fail criteria of fixing all issues by release and flawless execution of end-to-end user cases - Schedule and risks are also addressed. The plan is submitted for approval by Brian and Todd.

1. Post3D Release WK13Software QA Test Plan

2. ContentIdentifierIntroductionTest ItemsFeature to be testedFeatures not to be testedApproachVII. Item pass/failed criteriaVIII. Testing tasksIX. Environmental needsX. ScheduleXI. Risk assessmentXII. Approvals

3. I. IdentifierPresent QA TP is composed for Post3D.com release 3/28/11 and is a part of “Post3D” Product Plan

4. II. Introduction Current TP is designed to cover all required tests for items from “Post3D WK11 Release Notes”: https://3dvia.basecamphq.com/projects/5381357/file/75749936/post3d_wk11_releasenotes.xlsx 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 https://3dvia.basecamphq.com/projects/5381357/file/68389590/designcenter_sprint3_detail_v1.pptx

5. - Post3D Sprint 2 Details https://3dvia.basecamphq.com/projects/5381357/file/67858134/designcenter_sprint2_detail_final.pptx - Post3D Sprint 1 Details https://3dvia.basecamphq.com/projects/5381357/file/66950120/designcenter_sprint1_detail.pptx Additional info can be found on BaseCamp Post3d page: https://3dvia.basecamphq.com/projects/5381357/log

6. III. Test ItemsThe following is a list, by version and release, of the items to be tested: Current build version at time of testing: http://( 3DVIA Player build 2.10.53 Drop5, DB)

7. IV. Features to be testedJavascript changes(callback registration)Showcase User Management FeaturesWeb PurifySecurity Changes3DVIA Content UploadingDashboard content and appearanceUser’s email “Post” Features

8. 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.

9. 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 Manager2. 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) Friday3. QA Testing Term: 3/18 -3/27 (5 business day)

10. VII. Item Pass/Fail Criteria Program is considered “Pass” if main users flows worked according to the RequirementsAll 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.

11. 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)

12. IX. Environmental NeedsRM and VM : Windows 7 SP1, Windows XP SP2 , Windows XP SP3 (W510, DELL); IE7, IE8, FF3.5, Chrome 10;

13. Various testing tools(XENU, Nimbus etc.) X. Schedule

14. 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?

15. XII. APPROVALBrian _________________________Todd _________________________Date : __________________________