; Project Store
Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

Project Store

VIEWS: 4 PAGES: 35

Project Store document sample

More Info
  • pg 1
									The Metropolitan Museum of Art

The Met Store




Store 2004 Enhancements - Chapter 2 Test Plan


Version 1.0 Final




Author:   Chester Frankfeldt

          Elite Technical Services, Inc.
Store 2004 Enhancements - Chapter 2 Test Plan                             Page 2 of 35

Preface: Purpose and Scope of Document
The purpose of this document is to outline the approach to be used for testing the Store
2004 Enhancements Chapter 2. “Outline” will be the approach because of the
aggressive time frame for the project.

The document has the following purposes:

    Serve as a repository of information gathered at the start of test planning by the
       author, who is new to the project

    Inform all team members of the suggested approach and gain approval
      Ideally, serve as a continuing repository of the latest information until the test is
       completed

      Serve as a basis for future test plans.

The document will be revised as needed. It may never be “finished.” It is more
important to be current. However, it is planned that there will be enough material to
review before testing starts to be sure the approach is endorsed by all appropriate
parties.

The document history is on the next page followed by the Contents.

The sections of the document are listed in the Contents, and should be self-explanatory.

Words in italics are defined in the Glossary in Appendix B.

Paragraphs on a 25% gray background need further clarification or confirmation, or will
be completed later. Individual words may be automatically shaded as above, indicating
that they are fields, hyperlinks or cross-references to URLs, external documents, or
sections within the document. The links and cross-references make it convenient to
view this document electronically.

In draft versions the following notation will be used, in bold italics:

??Question to the reviewers

!!Comment to the reviewers




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                    Page 3 of 35

Document History
Change bars throughout the document indicate changes since the last version. Deleted
text will not be shown. In addition, minor changes, e.g., spelling, punctuation, or
grammar corrections, or removal of questions or comments, will not be marked.

 Version # Description                           Revised By              Date
1.0 Draft 1 First published draft                Chester Frankfeldt   6/29/04
1.0 Draft 2 Revisions throughout, e.g., adding   Chester Frankfeldt   7/1/04
            test log to status reporting
            process; addition of Appendixes
            B, C, D. E, draft of Test Case
            Form
1.0 Draft 3 Minor revisions to testing           Chester Frankfeldt   7/6/04
            procedure. Added test log and
            sample test cases.
1.0 Draft 4 Revisions to System Block            Chester Frankfeldt   7/8/04
            Diagram, Validation Matrix, Test
            Log
1.0 (Final) Revisions to System Block            Chester Frankfeldt   7/16/04
            Diagram, Test Log




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                Page 4 of 35

Contents

1  System Overview ......................................................................................... 6
      Figure 1: System Block Diagram ............................................................................ 6
2 Modifications Overview ............................................................................... 7
 2.1    SCOPE .................................................................................................................. 7
      Table 1. Scope of Modifications ............................................................................. 7
 2.2    SCHEDULE............................................................................................................ 7
      Table 2. Major Tasks in Order of Start Date .......................................................... 7
3 Roles and Responsibilities ......................................................................... 8
      Table 3. Roles and Responsibilities ........................................................................ 8
4 Test Overview ............................................................................................ 10
 4.1    SCOPE OF TEST .................................................................................................. 10
 4.2    TEST LEVELS ..................................................................................................... 10
   4.2.1 Requirements Validation ............................................................................... 11
 4.3    UNIT/FUNCTIONAL TEST - EXTERNAL................................................................ 11
   4.3.1 Objective ....................................................................................................... 11
   4.3.2 Entry Criteria ................................................................................................ 11
   4.3.3 Description .................................................................................................... 11
   4.3.4 Exit Criterion ................................................................................................ 11
 4.4    UNIT/FUNCTIONAL TEST - INTERNAL ................................................................. 12
   4.4.1 Objective ....................................................................................................... 12
   4.4.2 Entry Criteria ................................................................................................ 12
   4.4.3 Description .................................................................................................... 12
   4.4.4 Exit Criterion ................................................................................................ 12
 4.5    SMOKE TEST ...................................................................................................... 12
   4.5.1 Objective ....................................................................................................... 12
   4.5.2 Entry Criteria ................................................................................................ 12
   4.5.3 Description .................................................................................................... 13
   4.5.4 Exit Criterion ................................................................................................ 13
 4.6    SYSTEM TEST ..................................................................................................... 13
   4.6.1 Objective ....................................................................................................... 13
   4.6.2 Entry Criteria ................................................................................................ 13
   4.6.3 Description .................................................................................................... 13
   4.6.4 Exit Criterion ................................................................................................ 14
 4.7    USER ACCEPTANCE TEST ................................................................................... 14
   4.7.1 Objective ....................................................................................................... 14
   4.7.2 Entry Criteria ................................................................................................ 14


Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                             Page 5 of 35
    4.7.3 Description .................................................................................................... 14
    4.7.4 Exit Criterion ................................................................................................ 14
5 Management Processes ............................................................................ 15
  5.1    CONFIGURATION MANAGEMENT........................................................................ 15
    5.1.1 Objective ....................................................................................................... 15
    5.1.2 Description .................................................................................................... 15
  5.2    PROBLEM MANAGEMENT ................................................................................... 16
    5.2.1 Objective ....................................................................................................... 16
    5.2.2 Description .................................................................................................... 16
       Table 4. Severity Levels ....................................................................................... 16
  5.3    CHANGE MANAGEMENT .................................................................................... 17
    5.3.1 Objective ....................................................................................................... 17
    5.3.2 Description .................................................................................................... 17
  5.4    STATUS REPORTING ........................................................................................... 17
    5.4.1 Objective ....................................................................................................... 17
    5.4.2 Description .................................................................................................... 17
Appendix A. High Level Validation Matrix ...................................................... 19
Appendix B. Glossary ....................................................................................... 23
Appendix C. Problem Submission Form ........................................................ 24
Appendix D. Problem Log Matrix..................................................................... 25
Appendix E. Test Log Matrix ............................................................................ 26
Appendix F. Test Case Form............................................................................ 27
Appendix G. Sample Test Cases ..................................................................... 29




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
       Store 2004 Enhancements - Chapter 2 Test Plan                                        Page 6 of 35

       1 System Overview
       The Met Store structure is shown below. The diagram has had a major revision.\\

                                             Figure 1: System Block Diagram
              Administrative Site                                            Customer Site
                                       Administrator                 Customer
                                                           1



  Intranet
                            Update                                                  Order
                             Entry
                                                                                                      Internet
                                                                                    Entry

                                             E-mail
                                              File               4-hour
                 Internet                                       interval           Internet
                 Servers                                                           Servers
                              ++                                                                ++
           Win2K, ASP, C                                                        Win2K, ASP, C



                                         Order,
          Order                                              Order
                                       Ord. Arch.
      Status, Reject                                        Database
         E-Mails                       Databases
                                                           (SQL Server)
                                       (SQL Server)
                                                                                               Order
  Order                1                                                                    Acknowledge
  Reject                                                                                      E-Mails
   File                7 AM                      Product
                                                 Database
                                                (SQL Server)               Customer
                                                                           Database
           Merchweb                                                        (SQL Server)
             Pricing                             Cust. Svc.
            Database                             Sys. (CSS)
                                   Order
           (SQL Server)                          (SQL Server)                   Cust.           Warehouse
                                    File
                                                                                Svc.
                                                                                Rep
                                     Trail         Order                                    Shipper
                                                                 nightly
                                     File           File

  Credit                                  Order                                                          Pick
 Card Sys.                 Order        Proc. Sys.               Shipping                             Slips, etc.
(Nixdorf/UNIX)              File        (Mainframe)               System
                                                                (Mainframe)
                                                                                                      Bar Code


       Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
       Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 7 of 35

2 Modifications Overview
2.1 Scope
Referring to the System Block Diagram, the scope of the Chapter 2 modifications is as
follows:

                           Table 1. Scope of Modifications
          Component                      Changes?        Source of Changes
          Customer Side
          Web Servers                    Yes             Starpoint
          SQL Server                     Yes             Starpoint
          Admin Side
          Intranet Servers               Yes             Starpoint
          Admin Server                   Yes             Starpoint
          Merchweb Server                No??            N/A
          Nixdorf System                 Yes             Met internal work
          Mainframe CSS System           Yes             Met internal work

The requirements are found in the document Store 2004 Enhancements Ch 2 Spec with
Changes Accepted.doc.

2.2 Schedule
The major tasks are listed below. Completed tasks are shown in italics.

                     Table 2. Major Tasks in Order of Start Date
 Task                                                          Start      End
 Code and Install Met Internal Revisions                       ?/??/04    ?/??/04
 Unit/Function Test Met Internal Revisions                     ?/??/04    7/09/04
 Code and Unit/Function Test Starpoint Revisions               ?/??/04    7/09/04
 Develop Test Plan Version 1 Draft 1                           6/25/04    6/29/04
 Review Test Plan Version 1 Draft 1                            6/29/04    6/29/04
 Develop Test Plan Version 1 Draft 2                           6/30/04    7/01/04
 Develop Test Cases                                            7/02/04    TBD*
 Review Test Plan Version 1 Draft 2                            7/02/04    7/02/04
 Develop and Review Test Plan Version 1 Draft 3                7/06/04    7/06/04
 Develop and Review Test Plan Version 1 Draft 4                7/07/04    7/08/04
 Install Starpoint Enhancements                                7/12/04    7/12/04
 Test Starpoint Enhancements                                   7/13/04    8/13/04
 Install Enhancements in Production                            8/16/04    8/16/04

*This effort is not yet estimated, and may overlap with testing. There is a question
about how long the test planner will be allowed to work.



Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 8 of 35

3 Roles and Responsibilities
The following roles and responsibilities will apply to the test. Empty boxes indicate
information that is in general known by project managers at this point but not by the
author.

                           Table 3. Roles and Responsibilities
    Larry        212-650-2178 larry.kooper@metm      Manager,       technical
    Kooper                    useum.org              Internet       project
                                                     Technology     manager
    Janice       212-570-3856 janice.yablonski@m     Manager, e-    business
    Yablonski                 etmuseum.org           Commerce       project
                                                                    manager,
                                                                    user
                                                                    acceptance
                                                                    tester
    Barbara      212-650-2454 barbara.garces@me      assistant      user
    Garces                    tmuseum.org            head of e-     acceptance
                                                     business ?     tester
                                                     check
    !!will                                           e-business     user
    check                                            staff          acceptance
    w/Janice                                                        tester
    Chester    917-514-7238 chester.frankfeldt       N/A            test planner
    Frankfeldt
                                                                    test
                                                                    coordinator
    Larry                                                           system
    Kooper                                                          tester
    and/or
    Chester
    Frankfeldt
                                                                    Web test
                                                                    environment
                                                                    contact
    Don          212-386-0764 dspilky@starpoint.co                  Starpoint
    Spilky                    m                                     contact
    Laval Li     973-439-5332 lkim@aptegrity.com                    Aptegrity
    Ah Kim                                                          contact
                                                                    Nixdorf
                                                                    contact
                                                                    mainframe
                                                                    contact
1
If no domain, @metmuseum.org.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 9 of 35
The person filling the role of system tester is to be determined. It has been specified
that s/he will have some technical knowledge. However, while it would be
advantageous, the test planner may not fill this role.

The role of test coordinator has not been specified by the reviewers or agreed to at this
time. However, the test planner strongly recommends that such a role be filled, ideally
by the test planner.

These roles can be filled by the same person.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 10 of 35

4 Test Overview
4.1 Scope of Test
This test is focused on the changes coded by Starpoint.

Items referred to as Met Internal Work are not to be part of the test except in so far as
they interface with components receiving Starpoint changes.

4.2 Test Levels
Prior to final acceptance, the Chapter 2 Enhancements will have the levels of testing
listed below. The first two items are not controlled by this test plan but are described for
informational purposes.

      Unit Test/Functional Test of Met internal work to be performed by Met developers

      Unit Test/Functional Test of externally developed changes to be performed by
       Starpoint

      Smoke Test to be performed by temporary or permanent member(s) of the
       Museum staff

      End-to-End System Test to be performed by temporary or permanent member(s)
       of the Museum staff

      User Acceptance Test (UAT) to be performed by members of the e-business
       staff.

The tests are outlined below. Because of the aggressive time frame, the
Integration/System Test and the UAT will be overlapped.

The UAT will be conducted using the internal URLS under Internet Explorer 5.??latest
version and Internet Explorer 6.0, with emphasis on the latter.

      Test customer site: http://testweb

      Test admin site: http://97.0.101.161/Store/StoreHome.asp

The system test will be conducted using the above URLs as needed. Direct access to
the databases will be obtained as follows:

      Test customer site: ??need this

      Test admin site: ??need this

Test system will be set up to accept a specified “fake” credit card number. ??verify



Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 11 of 35
All tests are to include regression testing of all functions that employ changed system
components.

Certification of the completion of each test will be by e-mail by the test coordinator or
technical project manager to all key contacts.

4.2.1 Requirements Validation

While writing test cases, the test planner will note and report any questions or apparent
errors, conflicts or omissions in the specifications. These issues will be logged in the
document, Specification Issues.doc.

4.3 Unit/Functional Test - External
4.3.1 Objective

The objective of this test is to remove as many defects as possible before the Starpoint
changes are installed at the Museum.

4.3.2 Entry Criteria

      Unit testing is performed as units are coded.

      The overall functional test is performed as unit testing is completed and units can
       be interfaced.

4.3.3 Description

This test is to be performed by Starpoint on their own intranet. The system components
that can be tested are as follows:

      All Store 2004 Customer Site web pages

      Customer site database

      All Store 2004 Admin Site web pages

      Admin site database.

4.3.4 Exit Criterion
The exit criterion for this test is as follows:

      Removal of all errors detected, and successful retest.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 12 of 35

4.4 Unit/Functional Test - Internal

4.4.1 Objective

The objective of this test is to remove as many defects as possible before the System
Test and UAT begin.

4.4.2 Entry Criteria

      Unit testing is performed as changes are coded.

      The overall functional test is performed as unit testing is completed and units can
       be interfaced.

4.4.3 Description
This test is to be performed by staff at the respective sites. The system components
that can be tested are as follows:

      Nixdorf System

      Mainframe CSS System.

4.4.4 Exit Criterion

The exit criterion for this test is as follows:

      Removal of all errors detected, and successful retest.

4.5 Smoke Test
4.5.1 Objective

The objective of this test is to verify that installation has been successful enough for the
remaining testing, or production usage, to begin.

4.5.2 Entry Criteria

The entry criterion for this test is as follows:

      Certification by Starpoint that the Unit/Functional Test is complete.

      Certification by Aptegrity that the revised system has been successfully installed
       in the test environment.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                          Page 13 of 35

4.5.3 Description

The Smoke Test is a quick test of functions across the system. It is performed every
time there is a new installation in a Museum test or production environment.

The smoke test uses simple test scripts that can be run by anyone associated with the
project, however the best person to do this is the system tester. The purpose of using a
test script is to be sure that nothing is overlooked and that functions that may have been
missing or forgotten can be added to the test.

An order-of-magnitude estimate of how long it should take to execute a Smoke Test
script is 15 minutes.

Any problems found will be reported in the usual manner. However, if it is determined
that testing cannot continue, developers will be telephoned immediately.

As coding errors are removed from the system, the smoke test focuses increasingly on
detecting installation errors. In production installation, only the latter type of error
should occur, if any.

4.5.4 Exit Criterion

The exit criterion for the Smoke Test is determination by the tester that the system is
functioning sufficiently to allow System Testing and UAT to productively begin.

4.6 System Test
4.6.1 Objective

The objective of this test is to verify “under the covers” functions that cannot be directly
seen by the user. For the most part, this means that all data flows and database
transactions are working correctly.

4.6.2 Entry Criteria
The entry criteria for this test are as follows:

      Successful completion of the Smoke Test

      Approval of this test plan.

4.6.3 Description

A testing specialist will carry out this test, possibly with assistance from e-business staff.

Ideally, the System Test will be completely based on Test Cases. Please see Appendix
F. Test Case Form and Appendix G. Sample Test Cases. The test cases will be printed
and given to the tester(s) who will write in the results.


Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                       Page 14 of 35

4.6.4 Exit Criterion

The exit criterion for this test is as follows:

      Removal of all errors detected, and successful retest

4.7 User Acceptance Test
4.7.1 Objective

The objective of the UAT is suggested by its name. Normally, it would be the final test
prior to production installation.

4.7.2 Entry Criteria

The entry criteria for this test are as follows:

      Successful completion of the smoke test

      Approval of this test plan.

4.7.3 Description

Normally a UAT is best performed by actual users. For this project, Met e-commerce
staff will test both the Admin and Customer sites. They are users of the Admin site.
Although they are not normally users of the Customer site, they are more familiar with
the expected functionality than external customers would be, and they are the
customers for this project.

A testing specialist may participate in this test.

In order to assure coverage, the UAT will be partly based on Test Cases and partly
consist of ad hoc testing suggested by the testers’ knowledge of the system and the
expected changes. The test cases will be printed and given to the tester(s) who will
write in the results. Problems found in ad hoc testing will not be noted on test case
forms but will otherwise be handled in the same way as those found in executing test
cases.

4.7.4 Exit Criterion

The exit criterion for this test is as follows:

      Removal of all errors detected, and successful retest.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                             Page 15 of 35

5 Management Processes
Management processes are crucial, particularly in a situation where responsibility is
divided, e.g., where there are external developers. This section covers only those tests
being done at the Museum, as well as the production installation.

The Museum does not have existing documented processes. This section provides a
basic outline of the essential processes. It is not expected that they will be documented
in further detail.

5.1 Configuration Management
5.1.1 Objective

The purpose of configuration management is to assure that the correct version of each
module is placed in VSS and that the modules are correctly integrated and installed.

5.1.2 Description

Three types of source code are being used for the websites and databases. All will be
checked into VSS.

      C++, a coding language that requires compilation and is the only type that creates
       object modules to be stored in VSS

      ASP, which can generate/update web pages dynamically, e.g., when new
       products are added and does not require compilation

      SQL, which creates and updates tables and stored procedures by being
       executed in the SQL environment.

For initial installation, Starpoint will

      Electronically transmit the revised modules and pages to the test environment
       and check them into the VSS database.

      Electronically transmit an installation document listing the version of each module
       or page to be installed, and check it into VSS. A previous document that can be
       viewed as an example is Store 2004 Enhancements Ch 1 Installation Guide.doc.

Aptegrity will compile C++ modules and check the object code into VSS, and then
complete the installation.

For each system component, Starpoint will initially transmit all source modules and
pages, rather than changed items only.

For installation of fixes after the initial installation, Starpoint will normally transmit and
check into VSS only changed modules and pages, along with an updated installation


Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                         Page 16 of 35
document. If the revisions are small, the installation may be done by the technical
project manager, Larry Kooper, otherwise it will be done by Aptegrity.

There is a tradeoff between the goal of prompt availability of corrections and the goals
of stability and transparency – i.e., assuring that the test system functions reliably and
all concerned know what has been changed. It is recommended that changes to the
environment be made not more than once per day except for emergencies.

5.2 Problem Management
5.2.1 Objective

The objective of problem management is to assure that developers or others (e.g., test
lab contact) are notified of problems that need attention, and in turn that the testers are
notified that the problem has been fixed.

A secondary objective is to “keep score” on the process.

5.2.2 Description

A problem, or failure, is any situation where the system does not perform as expected.
Not all failures turn out to be code defects – some may be caused by environment,
installation or data issues.

To meet the first objective, the tester discovering the problem will electronically transmit
a problem form to the test coordinator, with screen prints attached as appropriate.
Please see Appendix C. Problem Submission Form.

                                 Table 4. Severity Levels

The following levels will be used:
 Code Name           Description                      Example
 H       High        Function does not work or        Order cannot be entered or
                     produces errors in the data      does not reflect correct
                                                      product
 M       Medium      Errors not affecting             Breadcrumbing omits one of
                     processing of data               the intermediate links
 L       Low         Error in presentation of         Text is the wrong color or
                     information                      font

The test coordinator will log the problem and e-mail the report to the appropriate contact
person for resolution.

The contact will notify the test coordinator by e-mail when a set of problems has been
fixed. It is expected that most coding problems will be fixed overnight.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                          Page 17 of 35
The log numbers of problems fixed will be transmitted to the testers by the test
coordinator when the fixes have been installed.

To meet the second objective, the test coordinator will maintain a problem log in an
Excel spreadsheet. A copy of this log can be seen in Appendix D. Problem Log Matrix.
The spreadsheet will be used as a source of information for status reporting. It will be
viewable on the server by all members of the project team, as SE CH2 Bug List.xls.

5.3 Change Management
5.3.1 Objective

The purpose of change management normally is to assure that changes are correctly
identified and approved.

5.3.2 Description
At this point in the Chapter 2 project, we do not anticipate changes other than problem
fixes. Rather than burden this project with undue formality, change management will be
confined to:

      Agreeing with Starpoint how frequently the system should be updated with fixes

      If needed, agreeing with Starpoint which changes should be installed at a given
       time

      Approval of intended changes by the technical project manager, Larry Kooper,
       prior to installation

      Notifying testers of changes that have been installed. The test coordinator will
       notify all concerned by e-mail.

No change request document will be employed other than the installation document.

5.4 Status Reporting
5.4.1 Objective

The objective of status reporting is to inform management and users of the progress of
the test, significant problems and successes, etc.

5.4.2 Description

In order to report status, it is essential that the test cases planned, created, run, and
whether passed or failed, be recorded. In order to do this, a test log matrix will be
created. The matrix will be initiated when test case writing begins.

Test cases will be planned by listing their descriptors in the matrix. Updates will record


Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                          Page 18 of 35

      Test cases developed

      Test cases assigned, with name of person assigned

      Test cases run or rerun, with dates, Pass/Fail and problem report numbers –
       responsibility for this update is to be assigned to either the testers or the test
       coordinator.

A preliminary version of this log is found in Appendix E. Test Log Matrix.

The spreadsheet will be used as a source of information for status reporting. It will be
viewable on the server by all members of the project team. It will be set up to provide
statistics automatically.

At an interval to be determined, weekly at minimum, the test coordinator will produce a
1 to 2 page, concise report supplemented as appropriate by attachments, e.g., data
from the current problem log and test case log.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                              Page 19 of 35

Appendix A. High Level Validation Matrix
The following matrix indicates, at a high level, which requirements will be part of each
test. The assumption is that the System Test and the UAT will each be subdivided into
builds which can be executed in parallel, where possible. An X in a column on the right
indicates that the build tests the requirement.


                                                                 Test Level
                                                            System          UAT




                                                   Bld. 1

                                                             Bld. 2

                                                                        Bld. 3

                                                                                 Bld. 4

                                                                                          Bld. 5

                                                                                                   Bld. 6

                                                                                                            Bld. 7

                                                                                                                     Bld. 8
 Requirement
 1. Dynamic Met Store Category Index Page                                                 X
 2. Breadcrumbing                                                                         X
 3. Monitoring                                     X
    3.1. DAILY STORE MONITORING EMAIL              X
      3.1.1. General                               x
      3.1.2. Live Site Order Counting              x
    3.2. REAL-TIME SERVICES MONITORING             X
    3.3. EMAIL HEARTBEAT                           X
    3.4. DAILY ORDER RECEIPT EMAIL [MET                               Previously Tested
    INTERNAL WORK]
 4. Search Engine Optimization
    4.1. META TAG GENERATION                                 X
      4.1.1. Description Meta Tag                            x
      4.1.2. Keywords Meta Tag                               x
    4.2. ALT TAGS                                            X
    4.3. TITLE TAGS                                          X
      4.3.1. For Product Family and Product                  x
      Category Pages
      4.3.2. For Other Store Pages [Met Internal             x
      Work]??Should we test this (assuming we
      can verify the tags at all)?




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                Page 20 of 35

                                                                   Test Level
                                                              System          UAT




                                                     Bld. 1

                                                               Bld. 2

                                                                          Bld. 3

                                                                                   Bld. 4

                                                                                            Bld. 5

                                                                                                     Bld. 6

                                                                                                              Bld. 7

                                                                                                                       Bld. 8
Requirement
   4.4. SEARCH ENGINE-FRIENDLY URLS                                       X
     4.4.1. General                                                       x
     4.4.2. Incoming Links                                                x
     4.4.3. Relative Links                                                x
     4.4.4. Parameters that must be preserved                             x
     4.4.5. Links to the store from other parts of                        x
     the site
     4.4.6. WebTrends Live Reports                                        x
   4.5. ROBOTS.TXT                                                        X
5. Rush Delivery                                                                   X        X
   5.1. WEB SITE AND EMAILS                                                        X        X
     5.1.1. Web Site                                                                        x
     5.1.2. Emails                                                                 x        x
   5.2. BACK-END SYSTEMS [MET INTERNAL
   WORK]
     5.2.1. Nixdorf order entry system [Met
     Internal Work]
     5.2.2. Customer Service Systems [Met Internal
                                                                        Previously Tested
     Work]
     5.2.3. Mail Order System [Met Internal Work]
     5.2.4. Shipping System (Pitney Bowes) [Met
     Internal Work]
6. New Shipping Location Descriptions                                              X  X
7. Expanded Web Order Number Range                                                 X  X
   7.1. WEB SITE                                                                      X
   7.2. BACK END [MET INTERNAL WORK]                                    Previously Tested
8. Don't Share Email Address (in checkout)                                    X       X
9. Store Customer Profile Database                                            X
   9.1. DATABASE DOCUMENTATION (CHANGES)                                      X
     9.1.1. New tables                                                        x
     9.1.2. Changes to existing database tables                               x
     9.1.3. Existing tables to be deleted                                     x
   9.2. CREATE EMAIL SUPPRESSION LIST, REMOVE                                 X
   FROM EMAIL SUPPRESSION LIST




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                           Page 21 of 35

                                                                Test Level
                                                           System          UAT




                                                  Bld. 1

                                                            Bld. 2

                                                                     Bld. 3

                                                                              Bld. 4

                                                                                       Bld. 5

                                                                                                Bld. 6

                                                                                                         Bld. 7

                                                                                                                  Bld. 8
Requirement
  9.3. INITIAL LOADING PROCESS FOR THE                                        X
  STORECUSTOMERPROFILE DATABASE
    9.3.1. Customers table                                                    x
    9.3.2. CustomerOrders table                                               x
    9.3.3. Copy No_Store_Email to Customers                                   x
    9.3.4. Update Customers Record from                                       x
    Guestbook
10. Checkout Summary                                                                            X
  10.1. CHECKOUT ADDRESS PAGE - FIGURES 4                                                       X
  AND 5
  10.2. ORDER REVIEW PAGE - FIGURE 6                                                            X
  10.3. THANK YOU PAGE - FIGURE 7                                                               X
Appendix A. Daily Store Monitoring Email                                      X
Appendix B. Events Met Store is Interested                                    X
in Monitoring
  B.1. METCATALOGREQUEST                                                      X
    B.1.1. Transfer Catalog Requests                                          x
    functionality
    B.1.2. Create text file functionality                                     x
  B.2. ORDERPROCESSOR                                                         X
    B.2.1. Transfer Orders Functionality                                      x
    B.2.2. Create Nixdorf File Functionality                                  x
  B.3. METPUBLISHINGSERVICE                                                   X
    B.3.1. Store Publishing Functionality                                     x
    B.3.2. Membership Data Import Functionality                               x
    B.3.3. Store Prices Import Functionality                                  x
  B.4. EMAIL DATA IMPORT                                                      X
    B.4.1. Connection made to CSS database                                    x
    B.4.2. Data is read in successfully                                       x




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                            Page 22 of 35

                                                                 Test Level
                                                            System          UAT




                                                   Bld. 1

                                                             Bld. 2

                                                                      Bld. 3

                                                                               Bld. 4

                                                                                        Bld. 5

                                                                                                 Bld. 6

                                                                                                          Bld. 7

                                                                                                                   Bld. 8
 Requirement
 Appendix C. Product Tags in Product Family                                    X
 Names
 Appendix D. Error Messages and                    X         X        X        X        X        X        X        X
 Informational Messages*
 Appendix E. Emails**
 Appendix F. Database Structure Changes
 Summary**


*??This section is missing from the spec. It is likely that checking error
messages will be part of each build.

**This section is a summary that does not add new information (will be verified.)




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                      Page 23 of 35

Appendix B. Glossary

Build       As used here, a group of test cases aimed at one or more high level
            requirements.
Coverage The extent to which a set of test cases exercises a set of requirements
Test Case A predetermined approach to testing a specified, limited subset of the
            requirements
Test Script A part of a test case that specifies to an appropriate level of detail the
            steps to be performed by the tester and the anticipated responses by the
            system.




Webproject$ on 'fscluster1\       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                Page 24 of 35

Appendix C. Problem Submission Form

   Starpoint CIS Program

   Bug Report – MMA-Store 2004 Enhancements Ch. 2
   Screen/Task:                                               Bug Date:
   Action:




   Expected Result:




   Actual Result:




   Comments




Webproject$ on 'fscluster1\                     69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                       Page 25 of 35

Appendix D. Problem Log Matrix


                                         Total Bugs

                                         Closed

                                         Open

                                         Open LK

                                         Open SP

                                         Change Order or Work Order

        Bug Nbr - Bug Number - Date  Filed                                                            Date
  W/N     Met       Starpoint Opened By Description                        Status                    Closed




Webproject$ on 'fscluster1\                                           69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                      Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                                Page 26 of 35

Appendix E. Test Log Matrix
There are two more columns at the left, not shown. The first contains the original requirement sequence number, so the table can be
unsorted if it is sorted. The second contains the requirement, allowing the matrix to function as a Detail Level Validation Matrix so that
requirements can be “checked off” as test cases are developed. This column is the same as the first column of Appendix A. In the
actual matrix, the Test Case #s are hyperlinks to the test case files to facilitate review.


Sys. UAT       Test                                              Written/                      Rerun    Date
Bld# Bld#     Case #   Test Case Name (Description)   Planned    Revised    Tested by            #      Run    Problem #s Comments




Webproject$ on 'fscluster1\                                                                69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                           Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                        Page 27 of 35

Appendix F. Test Case Form
The Metropolitan Museum of Art                                                                Test Case Form
Project: Store 2004 Enhancements - Chapter 2    Test: Sys.   UAT    Build #:     Test Case #:
Test Case Name:                                 Tested by:           Rerun #:     Date:

Test Setup:
Comments:


Test Step                                       Expected Result                                  P/F Prob. #
 1.
 2.
 3.
 4.
 5.
 6.
 7.
 8.
 9.
10.
11.
12.




Webproject$ on 'fscluster1\                                          69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                     Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                   Page 28 of 35

Test Step                                       Expected Result                            P/F Prob. #
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.




Webproject$ on 'fscluster1\                                       69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                  Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                             Page 29 of 35

Appendix G. Sample Test Cases
The Metropolitan Museum of Art                                                                                      Test Case Form
Project: Store 2004 Enhancements - Chapter 2                  Test: Sys.   UAT         Build #: 5      Test Case #:UAT05001
Test Case Name: Category Index Page                           Tested by:                Rerun #:        Date:

Comments:


Test Step                                                     Expected Result                                         P/F Prob. #
 1. Enter http://testweb in Address Bar                       Met user splash page appears
 2. Click on here in the first line                           Met user home page appears
 3. Click on The Met Store at left                            Met Store home page appears
 4. Scroll down (if needed) to Search the Met Store at left   Met Store Category Index link is seen just above the
                                                              line above that link
 5. Click on Met Store Category Index                         Category Index appears in main pane of page,
                                                              sorted by Category
                                                              Title at top is Met Store Category Index - The
                                                              Metropolitan Museum of Art - The Met Store
 6. Click on alphabetically in paragraph at top               Index is resorted alphabetically
 7. Scroll or navigate thru entire index                      Categories appear for most letters of alphabet,
                                                              indented 20 px (detailed check in System Test)
 8. Click on category in paragraph at top                     Index is resorted by categories
 9. Scroll through entire list                                Items are grey; there are two levels of indent. 2nd
                                                              level is twice the 1st level (50 and 100 px)
                                                              Categories are the same as those on the left
10. Click on several categories at random                     Each category links to its category page




Webproject$ on 'fscluster1\                                                              69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                         Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                Page 30 of 35


The Metropolitan Museum of Art                                                                        Test Case Form
Project: Store 2004 Enhancements - Chapter 2           Test: Sys.   UAT       Build #: 5    Test Case #: UAT05002
Test Case Name: Rush Delivery                          Tested by:              Rerun #:      Date:

Comments:


Test Step                                              Expected Result                                  P/F Prob. #
 1. Enter http://testweb in Address Bar                Met user splash page appears
 2. Click on here in the first line                    Met user home page appears
 3. Click on The Met Store at left                     Met Store home page appears
 4. Click on Gift Services                             Gift Services page appears
 5. Click on Gift Certificates icon                    Gift Certificates page appears
 6. Scroll to bottom                                   Select Product dropdown is seen
 7. Select a denomination and quantity, click ADD TO   Shopping Basket page appears with selection
    BASKET
 8. Click on CHECK OUT                                 Neither Express Delivery nor Rush Delivery
                                                       appears.
 9. Click Back button 4 times                          Met Store home page appears
10. Click on Membership at left                        Membership page appears; neither Express
                                                       Delivery nor Rush Delivery appears
11. Click Back button 4 times                          Met Store home page appears
12. Click on Met Store Category Index                  Category Index appears in main pane of page,
                                                       sorted by Category




Webproject$ on 'fscluster1\                                                    69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                               Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                     Page 31 of 35

Test Step                                                  Expected Result                                    P/F Prob. #
13. Choose a category and go as far as the Check Out       Neither Express Delivery nor Rush Delivery is
    page to purchase an item for delivery outside the 48   available on the Check Out page
    states
14. Click Back button 3 times                              Category Index appears in main pane of page,
                                                           sorted by Category
15. Choose a category and go through to purchase an item   Rush Delivery is available on the Check Out page
    for delivery in the 48 states
16. Select Rush Delivery and continue to Order Review      Rush Delivery is reflected on the Order Review
    page                                                   page subtotal
17. Complete order                                         Rush Delivery is reflected on the Thank You page
                                                           subtotal
18. Click Back button 4 times                              Met Store home page appears
19. Purchase a Gift Certificate as above, view basket      Shopping Basket page appears with selection
20. Purchase an item as above, view basket                 Shopping Basket page appears with both
                                                           selections
21. Go thru to Order Review page                           Informational message (text was TBD in spec)
                                                           appears




Webproject$ on 'fscluster1\                                                        69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                   Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                               Page 32 of 35


The Metropolitan Museum of Art                                                                                       Test Case Form
Project: Store 2004 Enhancements - Chapter 2                    Test: Sys.  UAT             Build #: 1      Test Case #:SYS01001
Test Case Name: Daily Store Monitoring E-Mail                   Tested by:                   Rerun #:        Date:

Comments:


Test Step                                                        Expected Result                                        P/F Prob. #
   Day 1
 1. Access daily e-mail distribution list within system          Distribution list is seen
    ??Note: It is to be determined where the list is kept
    and how/by whom it can be accessed/changed.
 2. Create an Outlook distribution list with the same            Distribution list is created.
    addressees
 3. Send an e-mail to all addressees asking if they have         E-mails are sent
    received the daily monitoring e-mail, attaching a copy of
    Appendix A. Note in the e-mail that this is for
    recognition only; they are not asked to do detailed
    verification. Send as High Importance, ask for reply
    ASAP.
 4. Examine replies                                              Affirmative replies are received from all
 5. Access daily e-mail distribution list within system          Distribution list is seen
 6. Add tester’s name to distribution list.                      Tester’s name is added




Webproject$ on 'fscluster1\                                                                  69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                             Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                       Page 33 of 35

Test Step                                                 Expected Result                                      P/F Prob. #
   Day 2:
 7. Examine Outlook In-Box                                Monitoring E-Mail has been received.
 8. Open Monitoring E-Mail                                E-Mail was sent at 9AM.
                                                          All items are included
                                                          Format is correct
 9. Examine data in E-Mail (??how to verify? Expect to    Data is correct
    have more steps looking at data sources.)
10.
11.
12. Access daily e-mail distribution list within system   Distribution list is seen
13. Remove tester’s name from distribution list.          Tester’s name is removed
      Day 3:
14. Examine Outlook In-Box                                Monitoring E-Mail has not been received.




Webproject$ on 'fscluster1\                                                           69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                      Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                           Page 34 of 35


The Metropolitan Museum of Art                                                                                    Test Case Form
Project: Store 2004 Enhancements - Chapter 2                  Test: Sys.  UAT         Build #: 1    Test Case #: SYS01002
Test Case Name: E-Mail Heartbeat                              Tested by:               Rerun #:      Date:

Comments:


Test Step                                                      Expected Result                                      P/F Prob. #
 1. E-mail lkim@aptegrity.com and ask him to to verify that    Positive response is received.
    e-mails from Admin and Live (customer) site are being
    received every 5 minutes.
 2. Turn off the sending of Admin Site e-mails ??check         Aptegrity opens a trouble ticket indicating that
    how. Note the time.                                        Admin Site e-mails have not been received since
                                                               the time noted
 3. Restore the sending of Admin Site e-mails. ??check         Positive response is received.
    how. Note the time.
    E-mail lkim@aptegrity.com and ask him to to verify that
    e-mails from Admin and Live (customer) site are being
    received every 5 minutes, and that admin site e-mails
    recommenced at the time noted.
 4. Turn off the sending of Live Site e-mails ??check how.  Aptegrity opens a trouble ticket indicating that Live
    Note the time.                                          Site e-mails have not been received since the time
                                                            noted
 5. Restore the sending of Live Site e-mails. ??check how. Positive response is received.
    Note the time.
    E-mail lkim@aptegrity.com and ask him to to verify that
    e-mails from Admin and Live (customer) site are being
    received every 5 minutes, and that admin site e-mails
    recommenced at the time noted.




Webproject$ on 'fscluster1\                                                            69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                       Last Revised: 7/18/11
Store 2004 Enhancements - Chapter 2 Test Plan                                                                             Page 35 of 35

Test Step                                                     Expected Result                                         P/F Prob. #
 6. Turn off the sending of both e-mails ??check how.         Aptegrity opens a trouble ticket indicating that both
    Note the time.                                            e-mails have not been received since the time
                                                              noted
 7. Restore the sending of both e-mails. ??check how.         Positive response is received.
    Note the time.
    E-mail lkim@aptegrity.com and ask him to to verify that
    e-mails from Admin and Live (customer) site are being
    received every 5 minutes, and that both e-mails
    recommenced at the time noted.




Webproject$ on 'fscluster1\                                                             69d2ca1f-58bd-4338-80fc-f7dfb1ee64c3.doc
Based on Req. Spec. V 1.0, VSS V. 22                                                                        Last Revised: 7/18/11

								
To top