Scribd Logo
Upload

Welcome to Scribd!

  • 12 views

    1.0 VASOP Tplan v1.01

    Uploaded by

    Priyanka Sahni
    The document outlines a test plan for the VASOP 1.0 software, including features to be tested such as registration, renewals, lab details, and reports. It describes the test strategy of both manual and automated testing, and provides details on test deliverables, tasks, schedule, and approvals required. The test plan is intended to ensure the key functionality of the VASOP 1.0 software operates as intended.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    1.0 VASOP Tplan v1.01

    Uploaded by

    Priyanka Sahni
    12 views4 pages
    The document outlines a test plan for the VASOP 1.0 software, including features to be tested such as registration, renewals, lab details, and reports. It describes the test strategy of both manual and automated testing, and provides details on test deliverables, tasks, schedule, and approvals required. The test plan is intended to ensure the key functionality of the VASOP 1.0 software operates as intended.

    Original Description:

    test

    Original Title

    1.0_VASOP_tplan_v1.01

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines a test plan for the VASOP 1.0 software, including features to be tested such as registration, renewals, lab details, and reports. It describes the test strategy of both manual and automated testing, and provides details on test deliverables, tasks, schedule, and approvals required. The test plan is intended to ensure the key functionality of the VASOP 1.0 software operates as intended.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    12 views4 pages

    1.0 VASOP Tplan v1.01

    Uploaded by

    Priyanka Sahni
    The document outlines a test plan for the VASOP 1.0 software, including features to be tested such as registration, renewals, lab details, and reports. It describes the test strategy of both manual and automated testing, and provides details on test deliverables, tasks, schedule, and approvals required. The test plan is intended to ensure the key functionality of the VASOP 1.0 software operates as intended.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 4

    1.Test Plan Identifier File Name: 1.0_VASOP_tplan_v1.0.doc Location: 2. Document History REV 1.

    0 Author Ashok Edits Initial Draft Date 15/12/02

    3. Intorduction VAS (Vidyala Automation Systems) is software product developed by INFIX SOLUTIONS for addressing various software needs of the Hospitals. This test plan will outline the features to be tested as part of outpatient details in the 1.0 release of VAS. 4. Features to be Tested Medium priority features are features that have been stable and High Priority features are features that have been recently changed. Feature To be Tested Registration Renewal Lab details X-ray details Scan details Abdominal Report Obsteric Scan Reports Priority High High Comments

    5. Features NOT to be Tested

    Help Contents will not be tested. Installation and presentation will not be tested. Support of the other architectures also will not be tested.
    6. Test Strategy The test strategy for VASOP1.0 will include manual testing with automated testing where time/need permits. Automated testing will be used to test the basic Interface objects, keyboard and mouse navigation or any redundant tasks best translated to automation. Automated testing will be limited to a Win-32 platform because of Automation tool limitations. Sanity test will include an very short battery of tests to ensure the VASOP1.0 runs/launches and can connect to the back end database. Test execution will happen as individual component testing. These tests will be fully automated.

    Acceptance tests will include a short battery of tests that will only touch major features to ensure VASOP1.0 will operate smoothly at a basic level. These tests will be executed on Windows 98, Windows NT 4, Windows 2000, workstations and servers. The goal will be to automate all of these tests. Full Functional tests will include a comprehensive test of all features listed in this document. These tests will be limited to the Windows 2000 workstation client. These test will include automation with time allowing.

    Functionality Testing Registration Verify New Registration Verify Modification of the existing record Verify Deletion of the existing record. Verify Searching of existing of records. Verify Refresh of the Data Fields. Verify Closing of the registration window. Renewal Verify Renewal of existing records. Verify Searching of existing of records. Verify Refresh of the Data Fields. Verify Closing of the registration window. Lab details X-ray details Scan details Abdominal Report Obsteric Scan Reports Usability Testing The usability testing will be accomplished by verifying the information in each window are accurate. Menus, icons and toolbar functionality will be tested as applicable to the navigation and results panes. Multi Window Overlapping will be tested because product supports opening of multiple documents. Robustness/Reliability Testing Test the GUI for correct keyboard and mouse navigation, windows, menus, buttons, etc. These tests will include Keyboard only navigation of VASOP1.0, Mouse only navigation. Correctness and existence of warning/error dialog boxes. The correct/expected functionality of buttons, icons and menus. Stress Testing Not applicable

    7.Test Deliverables
    Test plan Test Specification 1.0_VASOP_tplan.doc 1.0_VASOP_tspec.doc

    Test Automation Plan Test Checklist Test Logs Test tools

    TBD TBD TBD Scripts, Segue SILK Test Tool

    8.Testing Tasks & Resource Needs


    Use of MS ACCESS database. Write Test Specification. Write Test Automation plan. Write Test Checklist. Setup workspace. Develop Automation script. Minimum requirements for platforms: Intel: Intel ~400mz, with 96mb* of Ram for NT workstation client. Intel ~400mz, with 64mb *of Ram for 98 workstation client. (* Automation needs an additional 128MBs to function)

    9.Schedule
    Test Documentation
    Document Development Time Person-Days Test Plan Test Specifications Test Logs Test Summary Report Checklist 4 days 7 days TBD TBD TBD Completion Date 12/20/2002 Functional Spec. Review Testplan, Functional Spec, Review Sign-off Date Dependencies

    Test Development
    Deliverable Functional Test Suite Automation 5 Development Time Person-Days Completion Date Dependencies

    Test Execution
    Test Activity Alpha Acceptance Functional Functionality Usability Robustness Stress Multi Inst. Regression Documentation Review Total Test Cycle 2? 8 2? 8 2? 6 3 Days 5 All High to Medium testcaces Execution Time (Person-Days) Beta 3 Days 4 FCS 4 Days Srihari, Srinu Dependencies

    10. Issues/Risks and Contingencies


    RISK Any Automation will need to be created in parallel of testing. VB Accessibility Utilities and specs to verify compliance to Accessibility are not available. CONTINGENCY Manual testing COMMENTS Goal is to add Automation where possible. Initial setup might be able to be worked on in an earlier stage if time permitting. Simplistic tests? Accessibility guidelines are not specified in spec.

    11.Approvals
    POSITION * Approval Required NAME SIGNATURE REVIEWED APPROVED

    Tech Lead STAFF ENG, SW MTS, SW

    Siva Srinu Srihari

    12. References
    VAS1.0 User Interface Specification VAS1.0 Functional Specification VAS1.0 Design Specification

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy