Test Plan and Cases (TPC)

Test Plan and Cases (TPC) Version 1.3 Version no x.xx

Test Plan and Cases (TPC)

FlowerSeeker

Team 5

Name / Roles
Eder Figueroa / Primary Role: Project Manager/ Implementer.
Secondary Role: Tester.
Sophia Wu / Primary Role: Tester/ Trainer
Secondary Role: Implementer
Doris Lam / Primary Role: IIV&Ver/ Quality Focal Point/ Implementer.
Secondary Role: Tester.
Hiram Garcia / Primary Role: IIV&Ver/ Quality Focal Point/ Implementer.
Secondary Role: Tester.

02/20/2013

Version History

Date / Author / Version / Changes made / Rationale /
12/02/12 / DL / 1.0 / ·  Added Introduction and test cases / ·  Initial version with test cases
12/10/12 / DL / 1.1 / ·  Added user registration test cases and updated dependencies / ·  Test case was missing
02/11/13 / SW, DL / 1.2 / ·  Revised cover, filled in Section 2 and 4 / ·  Reform development team, RDCP updates
02/20/13 / DL / 1.3 / ·  Revised some test cases’ input and output / ·  Updated test cases based on new information and changed requirements

Table of Contents

Test Plan and Cases (TPC) i

Version History ii

Table of Contents iii

Table of Tables v

Table of Figures vii

1. Introduction 8

2. Test Strategy and Preparation 9

2.1 Hardware preparation 9

2.2 Software preparation 9

2.3 Other pre-test preparations 9

2.4 Requirements Traceability 10

3. Test Identification 11

3.1 TC-01 Authentication 11

3.2 TC-02 Search 12

3.3 TC-03 Create Florist Profile 14

3.4 TC-04 Add Product 16

3.5 TC-05 Show Customers 17

3.6 TC-06 Subscription 19

3.7 TC-07 Florist Order History 20

3.8 TC-08 Place Order 22

3.9 TC-09 Rank and Review 23

3.10 TC-10 Customer Order History and Tracking 25

3.11 TC-11 Admin Capabilities 26

3.12 TC-12 Customer Registration 27

4. Resources and schedule 29

4.1 Resources 29

4.2 Staffing and Training Needs 29

4.3 Schedule 29

5. Test Case Dependency Graph 30

21

TPC_RDCP_S13b_T05_V1.3.doc 02/20/13

Test Plan and Cases (TPC) Version 1.3 Version no x.xx

Table of Tables

Table 1: Requirements Traceability Matrix 10

Table 2: TC-01-01 Login 11

Table 3: TC-01-02 Incorrect Login 12

Table 4: TC-01-03 Logout 12

Table 5: TC-02-01 Search by location 13

Table 6: TC-02-02 Search by price 13

Table 7: TC-02-03 Search by occasion 14

Table 8: TC-02-04 Search by rating 14

Table 9: TC-03-01 Register new florist 15

Table 10: TC-03-02 Register florist failure 15

Table 11: TC-04-01 Add new product 16

Table 12: TC-04-02 Add invalid product 17

Table 13: TC-05-01 Show customer list 18

Table 14: TC-05-02 Show customer detail 18

Table 15: TC-05-03 Generate coupon 18

Table 16: TC-06-01 Add premium subscription 19

Table 17: TC-07-01 Florist Order History 20

Table 18: TC-07-02 Florist Order Detail 21

Table 19: TC-07-03 Update Order Status 21

Table 20: TC-08-01 Add to cart 22

Table 21: TC-08-02 Checkout 22

Table 22: TC-08-03 Checkout failure 23

Table 23: TC-09-01 Rank product 24

Table 24: TC-09-02 Review product 24

Table 25: TC-10-01 Customer Order History 25

Table 26: TC-10-02 Customer Order Detail 25

Table 27: TC-11-01 Premium subscribers info 26

Table 28: TC-12-01 Register new customer 27

Table 29: TC-12-02 Register customer failure 28

21

TPC_RDCP_S13b_T05_V1.3.doc 02/20/13

Test Plan and Cases (TPC) Version 1.3 Version no x.xx

Table of Figures

Figure 1: Test Case Dependency Graph 30

21

TPC_RDCP_S13b_T05_V1.3.doc 02/20/13

Test Plan and Cases (TPC) Version 1.3

1.  Introduction

This document provides the test cases and preparations needed to conduct a system level acceptance test of the FlowerSeeker project. The purpose is to verify that the agreed upon requirements captured in Winbook have been met. The scope of testing described in this document will include all capabilities and level of service requirements captured, and will not include low level tests like unit tests or integration test, nor schedule or budget constraints. The focus of testing will be on use cases as outlined in the SSAD and the corresponding win conditions in Winbook.

2.  Test Strategy and Preparation

The test strategy includes value based test prioritization and requirements-test traceability. Testing of functionalities deemed most important to the client will be prioritized along with their prerequisites. Requirements traceability will provide the evidence that a requirement has been met when its test is passed. Testing will focus on user scenarios and their corresponding invalid input/error cases.

2.1  Hardware preparation

There is no specific hardware required for testing. Testing will be performed on builders’ and testers’ development machines and on staging environment hosted by Amazon web services.

2.2  Software preparation

A tester’s machine will need to be able to run the FlowerSeeker web application locally with a MySQL database. It will also need to be able to get the latest source code and artifacts from Bitbucket using the Git version control system. The machine should have the following installations:

·  Eclipse EE IDE, with EGit and maven plugins (optional but recommended)

·  MySQL 5.5.x

·  Java 6

·  Tomcat 7

·  Latest version of various browsers (Safari, Chrome, Firefox, IE) available on tester’s system

The tester can checkout specific versions or the latest version of source code using Git and build the war file needed, or run the application from within Eclipse itself. Using a browser, perform the test cases listed in this document as user scenarios. Tester can also choose to write applicable automated test code and run them as regression tests, create a data generator that prepopulates the database, or use Selenium to automate browser GUI tests.

2.3  Other pre-test preparations

None

2.4  Requirements Traceability

Table 1: Requirements Traceability Matrix

Requirement ID / Verification Type / Test Case ID (if applicable)
WC_2275 / Testing / TC-01 Authentication
WC_1398, WC_1445, WC_1400, WC_1446 / Testing / TC-02 Search
WC_1460, WC_1457, WC_1456, WC_1458 / Testing / TC-03 Register Florist
WC_1459, WC_1456, WC_1407 / Testing / TC-04 Add Product
WC_1462, WC_1399 / Testing / TC-05 Show Customers
WC_1466 / Testing / TC-06 Subscription
WC_1444, WC_1461 / Testing / TC-07 Florist Order History
WC_1463 / Testing / TC-08 Place Order
WC_1451 / Testing / TC-09 Rank and Review
WC_1406, WC_1412 / Testing / TC-10 Customer Order History
WC_1467 / Testing / TC-11 Admin Pages
WC_2275 / Testing / TC-12 Customer Registration

3.  Test Identification

All test cases in this section have the assumption that the user has internet access and the FlowerSeeker site is online with no hosting problems.

3.1  TC-01 Authentication

3.1.1  Test Level

Software Item Level

3.1.2  Test Class

Functionality Test

Erroneous Test

3.1.3  Test Completion Criteria

-  The system will login the user when the correct username and password are provided

-  The system will display an error to the user when incorrect login info is provided

-  The system will remember user session until the user logs out

3.1.4  Test Cases

Table 2: TC-01-01 Login

Test Case Number / TC-01-01 Login
Test Item / User Authentication
Test Priority / Must have
Pre-conditions / User is not already logged in and is on the login page, user has registered
Post-conditions / User is logged in
Input Specifications / Username and password
Expected Output Specifications / The username is displayed somewhere on the page the user was trying to get to if login is correct
Pass/Fail Criteria / Fail if the system displays any error when given a correct username and password
Assumptions and Constraints / None
Dependencies / TC-03-01, TC-12-01
Traceability / WC_2275

Table 3: TC-01-02 Incorrect Login

Test Case Number / TC-01-02 Incorrect Login
Test Item / User Authentication
Test Priority / Must have
Pre-conditions / User is not already logged in and is on the login page, user has registered
Post-conditions / User is not logged in, an error message is displayed
Input Specifications / Incorrect username or password
Expected Output Specifications / An error message stating user has entered invalid credentials
Pass/Fail Criteria / Fail if the system logs in user
Assumptions and Constraints / None
Dependencies / TC-03-01
Traceability / WC_2275

Table 4: TC-01-03 Logout

Test Case Number / TC-01-03 Logout
Test Item / User Authentication
Test Priority / Must have
Pre-conditions / User is logged in
Post-conditions / User is logged out
Input Specifications / User clicks the logout button
Expected Output Specifications / User is logged out and system redirects to home page
Pass/Fail Criteria / Fail if user can still access restricted pages when logged out
Assumptions and Constraints
Dependencies / TC-01-01, TC-12-01
Traceability / WC_2275

3.2  TC-02 Search

3.2.1  Test Level

Software Item Level

3.2.2  Test Class

Functionality Test

Erroneous Test

3.2.3  Test Completion Criteria

-  The system returns search results based on inputted search criteria (location, occasion, price, or ranking)

-  The system will display search results as clickable links on a webpage to the user

-  The result links, when clicked, will take the user to the corresponding florist or product page

3.2.4  Test Cases

Table 5: TC-02-01 Search by location

Test Case Number / TC-02-01 Search by location
Test Item / Search module
Test Priority / Must have
Pre-conditions / Some florist profiles have been created with location information, the search by location page is displayed
Post-conditions / A list of products that match input search location is returned for display to the user
Input Specifications / A zip code to search for
Expected Output Specifications / Links to products that are sold by florists that serve the specified zip code area
Pass/Fail Criteria / Fail if no product link is displayed, or the wrong products are displayed
Assumptions and Constraints / Florist profiles will include all the zip code they serve
Dependencies / TC-03-01
Traceability / WC_1398

Table 6: TC-02-02 Search by price

Test Case Number / TC-02-02 Search by location
Test Item / Search module
Test Priority / Must have
Pre-conditions / Some products from florists have been created with price information, search by price page is displayed
Post-conditions / A list of products that match input price range is returned for display to the user
Input Specifications / A price range
Expected Output Specifications / Links to product pages with price in user’s search range
Pass/Fail Criteria / Fail if no products are displayed, or wrong products are displayed
Assumptions and Constraints / None
Dependencies / TC-04-01, TC-01-01, TC-03-01
Traceability / WC_1445

Table 7: TC-02-03 Search by occasion

Test Case Number / TC-02-03 Search by occasion
Test Item / Search module
Test Priority / Must have
Pre-conditions / Some products from florists have been created with occasion information
Post-conditions / A list of products that match input search occasion, occasion drop down list is shown
Input Specifications / The occasion to search for
Expected Output Specifications / Links to product pages that match the occasion searched for
Pass/Fail Criteria / Fail if no products are displayed, or products with wrong occasion are displayed
Assumptions and Constraints / None
Dependencies / TC-04-01, TC-01-01, TC-03-01
Traceability / WC_1400

Table 8: TC-02-04 Search by rating

Test Case Number / TC-02-04 Search by rating
Test Item / Search module
Test Priority / Must have
Pre-conditions / Some products have been created and rated, user is on search by rating page
Post-conditions / A list of florists with equal or higher average rating for their products are displayed
Input Specifications / Click on the number of stars as minimum rating
Expected Output Specifications / Links to florists with average rank for products matching rating or higher are displayed
Pass/Fail Criteria / Fail if no florists are displayed, or florists with lower rating are displayed
Assumptions and Constraints / None
Dependencies / TC-09-01, TC-01-01, TC-03-01, TC-12-01
Traceability / WC_1446

3.3  TC-03 Create Florist Profile

3.3.1  Test Level

Software Item Level

3.3.2  Test Class

Functionality Test

Erroneous Test

3.3.3  Test Completion Criteria

-  The system allows new florists to create a profile with name, store name, store address, area served, email, phone, and store times

-  The system will not create duplicate florist profiles or profiles with missing or malformed information

3.3.4  Test Cases

Table 9: TC-03-01 Register new florist

Test Case Number / TC-03-01 Register new florist
Test Item / Florist management
Test Priority / Must have
Pre-conditions / Florist is on register new florist page
Post-conditions / A florist profile is created with florist information
Input Specifications / Florist username, store name, email, address, locations served, store times, phone, password
Expected Output Specifications / The florist profile page is displayed and confirmation email sent to florist’s email
Pass/Fail Criteria / Fail if all information are inputted and system was unable to create a new florist entry
Assumptions and Constraints / Florist entered info are not duplicates of existing florist
Dependencies / None
Traceability / WC_1460, WC_1457, WC_1456, WC_1458

Table 10: TC-03-02 Register florist failure

Test Case Number / TC-03-02 Register florist failure
Test Item / Florist management
Test Priority / Must have
Pre-conditions / Florist is on register new florist page
Post-conditions / Error message is displayed for florist already in system
Input Specifications / Florist username, store name, email, address, locations served, phone, password
Expected Output Specifications / Error page is shown indicating florist inputted info already match an existing florist or what info are missing
Pass/Fail Criteria / Fail if new profile is created
Assumptions and Constraints / None
Dependencies / TC-03-01
Traceability / WC_1460, WC_1457, WC_1456, WC_1458

3.4  TC-04 Add Product

3.4.1  Test Level

Software Item Level

3.4.2  Test Class

Functionality Test

Erroneous Test

3.4.3  Test Completion Criteria

-  The system allows registered and logged in florists to create new products with product name, image, occasion category, and price

-  The system will not allow new product to be created with missing information

3.4.4  Test Cases

Table 11: TC-04-01 Add new product

Test Case Number / TC-04-01 Add new product
Test Item / Florist management and product management
Test Priority / Must have
Pre-conditions / Florist is logged in and clicked the add product link on their profile page, possible occasion selections are already in database
Post-conditions / A new product is created and associated with the florist
Input Specifications / Product name, an image, associated occasion, price
Expected Output Specifications / New product is shown on florist’s profile page
Pass/Fail Criteria / Fail if the system displays any error when all information required are filled in
Assumptions and Constraints / Inputted info are not malformed
Dependencies / TC-01-01, TC-03-01
Traceability / WC_1459, WC_1456, WC_1407

Table 12: TC-04-02 Add invalid product