1. Overall interface systems with GPS
    1. Jaguar
    2. PPL
    3. Ceiton
    4. Rights mart
    5. WebStor
    6. Word Press
    7. International channel partner
    8. International sales site
    9. Media pulse
    10. Platform
    11. Image View
    12. Netstorage
  2. Control Procedures
    1. Reviews
      1. The project team will perform reviews for each Iteration. (Test Case Review and Final Test Summary Review). A meeting notice, with related documents, will be emailed to each participant
    2. Bug Review meetings
      1. The project team will perform reviews for each Iteration. (Test Case Review and Final Test Summary Review). A meeting notice, with related documents, will be emailed to each participant
    3. Change Request
      1. Once testing begins, changes to the GPS system are discouraged. If functional changes are required, these proposed changes will be discussed with the managers The managers will determine the impact of the change and if/when it should be implemented. The additional/modified fucnitonality should be documented as the Change Request document
    4. Defect Reporting
      1. When defects are found, the testers will complete a defect report on the JIRA defect tracking system. JIRA is accessible by testers, developers & all members of the project team. When a defect has been fixed or more information is needed, the developer will change the status of the defect to indicate the current state. Once a defect is fixed by developers the testers would re-test close the defect report if it passes. Below diagram explains the defect lifecycle D- Developers, T-Testers, PM- Project Managers
      2. Bug LifeCycle
  3. Test Schedule (Dates only for representation)
    1. Iteration 1
    2. 09/01/2015
    3. 20/03/2015
    4. Dhiren Shah
    5. Robinson Batchu
    6. Iteration 2
    7. Iteration 3
  4. Introduction
  5. Test Plan Objectives
    1.  Define the activities required to prepare for and conduct smoke, functional, system, interface and webservices testing.
    2.  Communicate to all responsible parties about the System Test strategy
    3.  Define deliverables and responsible parties
    4.  Communicate to all responsible parties the various Dependencies and Risks
  6. Scope
    1. In Scope
      1. The overall purpose of testing is to ensure the new web based system, GPS meets all of its technical, functional and business requirements. The purpose of this document is to describe the overall testplan and strategy for testing GPS. The approach described in this document provides the framework for all testing related to this application. Individual test cases will be written for each iteration based on the use cases provide by Virtusa (vendor) team. The test plan document will also be updated as required for each release if there are any improvements/ modifications along with the change request document
    2. Out Of Scope
      1. Load Testing
      2. Automation Testing
  7. Environment Requirements
    1. Environment Requirements
        1. 1
        2. Web Server
        3. AEWEBSVCDEV4
        4. Installation of the application
        5. Net – 4.5 IIS – 7.5 OS – Win2008R2
        6. Intel(R) Xenon, 4 GB RAM, 30 GB HDD
        7. 1
      2. 2
      3. App Server
      4. AEWEBAPPIDDEV
      5. Managing application data
      6. Net – 4.5 IIS – 7.5 OS – Win2008R2
      7. Intel(R) Xenon, 4 GB RAM, 30 GB HDD
      8. 1
      9. DB Server
      10. 3
      11. DEVSQLCL2A\ DEVINST2A
      12. Database server to support the Content Management Tool
      13. OS - Win2008R2 MS SQL Server 2008 R2
      14. Intel(R) Xenon, 4 GB RAM, 30 GB HDD
      15. 1
      16. 4
      17. QA Requirements
      18. UT1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others) DB – ut1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others)
      19. UT1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others) DB – ut1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others)
      20. UT1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others) DB – ut1 for GPS and Other systems (PPL, Jaguar, MediaPulse and others)
  8. Test Strategy
    1. Entry Criteria
      1.  All business requirements are documented and approved by the business users
      2.  All design specifications like BRD, Use Cases, Wireframes have been reviewed and approved
      3.  Unit testing has been completed by the development team
      4.  All hardware needed for the test environment is available
      5.  The application delivered to the test environment is of reliable quality
      6.  Initial smoke test of the delivered functionality is approved by the testing team
      7.  Code changes made to the test site will go through a change control process
    2. Exit Criteria
      1.  All test scenarios and test cases have been completed successfully
      2.  All issues prioritized and priority 1 issues resolved
      3.  All outstanding defects are documented in a test summary with a priority and severity status
      4.  Go/No-go meeting is held to determine acceptability of product
    3. Test Execution
      1. Smoke Testing
        1. The released code is working properly and ensures the system is basically operational.The QA environment is properly configured
      2. Functional Testing
        1. Functional testing focuses on the functional requirements of the software and is performed to confirm that the application operates accurately according to the documented specifications and requirements, and to ensure that interfaces to external systems are properly working
      3. Interface Testing
        1. This testing follows a transaction through all of the product processes that interact with it and tests the product in its entirety. Interface testing shall be performed to ensure that the product actually works in the way a typical user would interact with it. This involves the webservices testing
      4. System Testing
        1. Testing the fully integrated applications including external peripherals in order to check how components interact with one another and with the system as a whole. This is also called End to End testing. Verify thorough testing of every input in the application to check for desired outputs. Testing of the user's experience with the application
      5. Cross Browser Testing
        1. Please find below the scope of browser testing Target Design Resolution is 1280x800 and it should work with any screen resolution
          1. Iteration 1
          2. • IE 9 and IE10 • Safari 5.1.7 and Latest Version of Safari • Chrome 37 and Latest Version of Chrome • Mozilla 30 and Latest Version of Mozilla
          3. Latest Version of Chrome
          4. Iteration 2
          5. Latest Version of Chrome
          6. • IE 9 and IE10 • Safari 5.1.7 and Latest Version of Safari • Chrome 37 and Latest Version of Chrome • Mozilla 30 and Latest Version of Mozilla
          7. Iteration 3
          8. • IE 9 and IE10 • Latest Version of Safari • Latest Version of Chrome • Latest Version of Mozilla
          9. • IE 9 and IE10 • Safari 5.1.7 and Latest Version of Safari • Chrome 37 and Latest Version of Chrome • Mozilla 30 and Latest Version of Mozilla
      6. Regression Testing
        1. Regression testing shall be performed at the end of Iteration 3 to verify that previously tested features and functions do not have any new defects introduced, while correcting other problems or adding and modifying other features
      7. User acceptance testing
        1. User acceptance testing activities will be performed by the business users. The purpose of this testing will be to ensure the application meets the users’ expectations. This also includes focuses on usability and will include; appearance, consistency of controls, consistency of field naming, accuracy of drop down field information lists, spelling of all field name/data values, accuracy of default field values, tab sequence, and error/help messages
    4. Test Organization
      1. Test Types
        1. Smoke Testing
        2. UI and Functional Testing (UI and Database testing)
        3. Interface Testing (Web Services Testing)
        4. System Testing
        5. User Acceptance Testing
      2. Constraints
        1. Frequent change in the requirements
        2. Unavailability of Test Data
        3. Unavailability of Test Environment
    5. Test Case Development
      1. Test Case ID
      2. Module
      3. Test Name
      4. Test Data
      5. Action
      6. Expected Result
      7. Test Result
      8. Comments
      9. Use Case
    6. Requirement Tracebility Matrix
  9. Tools
    1. Subtopic 1
      1. 1
        1. DB
        2. SQL Server 2008
      2. 2
        1. Defect management
        2. JIRA
      3. 3
        1. Test Management
        2. Excel (Test Summary Report)
  10. Functions To Be Tested
    1. Iteration 1
      1. Deals
      2. Deal Offer
      3. Programming
      4. Tiered Pricing
      5. Orders
    2. Iteration 2
      1. Fulfillment
      2. PPL-GPS Integration
      3. Deals Offer – Mobile View
      4. Media Pulse-GPS Integration
      5. Images Media
      6. WIP
      7. NWCO-GPS Integration
      8. Short Form Deals
      9. PPL-GPS Integration
      10. RDM-GPS Integration
      11. Jaguar-GPS Integration
      12. Please refer to the link for the latest project plan implementation plan for more details
    3. Iteration 3
      1. Production
      2. Referential Data Mgmt
      3. Reports
      4. Global Search Updates
      5. UCA Requirements
    4. S.No. Functional Requirement Criticality 1 Provide text search solution using data in the IDB High 2 Provide faceted navigation of search results High 3 Provide ability to export search results in MS Excel Medium 4 Provide ability to export search results in PDF Medium 5 Provide view of search results items using read-only international screens or links to other systems Medium 6 Read only episodic information view from PPL Medium 7 Automatically consume Episode Rights information from Rights Data mart including off-net/on-net High 8 Automatically retrieve and view information for international Assets High 9 Create/Update/View international assets information for episodes High 10 Add/View fulfillment assets for episodes High 11 Tag keywords for international episodes searchable from website Medium 12 View/Update rights information in international master High 13 View/Update attributes information from jaguar with expiration Date for each region High 14 Associate support documents from PPL/Debut to international episodes High 15 Queue programs for Int’1 production High 16 Push information for Int’1 Master to Media Pulse(Metadata and asset ) High 17 Identify vendor Information based on Business Logic High 18 Search Orders/Assignment/Tasks by episode metadata Medium 19 Create/Update/View/Assignments for production Medium 20 Create/Update/View Tasks for Assignment for multiple reels High 21 View Production tech Spec Medium 22 View/create/Update Worksheet with multiple reels for each episode Medium 23 Search programming information based on latest quarter release Medium 24 Add New Digital Assets available for episodes/programs High 25 Update digital asset association to episodes/Programs/Channels to be viewed in Int’1 Website High 26 Maintain source information for royalty payments High 27 Create XML from tech spec to match existing requirements for DMC Medium 28 Improve image workflow Medium 29 Responsive Design for approximately 20% of Sale Forms High 30 Mobile entry – entry to be like transactional entry and not web entry High 31 Tiered pricing module High 32 Integrate URL Reporting Dashboard High 33 Integrate existing (UCA) contact administration for GPS High
      1. Subtopic 1
        1. Subtopic 1
  11. Please refer to the below link for the latest project plan implementation schedule