Test Plan and Cases (TPC) - University of Southern California · Test Plan and Cases (TPC) Fuppy Team No.7 Krupa Patel ... Post-conditions Establish Integration to API to retrieve

Test Plan and Cases (TPC)

Fuppy

Team No.7

Krupa Patel (Product Manager)

Adil Assouab (Requiremnt Engineer)

Yiyuan Chen (Software Architecture)

Praveen Chander (Designer/Prototyper)

Zhouyun Feng (Developer)

Fereshteh Khorzani (Quality Focal Point)

November 30, 2016

TPC_TRR_F16a_T07_V1.0.docx

ii

Version History

Date Autho

r

Versio

n

Changes made Rationale

11/30/1

6

PC 1.0 Original template for use with

CSCI577 v1.5

Initial draft for use with

CSCI577 v1.5


iii

Table of Contents

TEST PLAN AND CASES (TPC) .........................................................................................I

VERSION HISTORY .......................................................................................................... II

TABLE OF CONTENTS .................................................................................................... III

TABLE OF TABLES .......................................................................................................... V

1. Introduction ........................................................................................................................... 7

2. Test Strategy and Preparation ............................................................................................... 8

2.1 Hardware preparation ..................................................................................................... 8

2.2 Other pre-test preparations ............................................................................................. 8

2.3 Requirements Traceability ............................................................................................. 9

3. Test Identification ............................................................................................................... 10

3.1 TC-UI-01 Search Function ........................................................................................... 10

3.2 TC-UI-02 Data from Petfinder API ............................................................................. 13

3.3 TC-UI-03 Search functionality performance ............................................................... 14

3.4 TC-L-01 Displaying a list of pets ................................................................................. 15

3.5 TC-L-02 Detailed information from Petfinder ............................................................. 16

3.6 TC-L-03 Traverse Fetched Data .................................................................................. 17

3.7 TC-G-01 Display correct address in google map ......................................................... 19

3.8 TC-G-02 Correctness in Shelter Page UI ..................................................................... 20

3.9 TC-G-03 Check Shelter information ............................................................................ 21

3.10 TC-I-01 Fuppy Search Functionality ........................................................................... 22

3.11 TC-AU-01 User Authentication ................................................................................... 25


iv

3.12 TC-A-01 Appointment System .................................................................................... 29

3.13 TC-A-02 Load Balance Check ..................................................................................... 31

4. Resources and schedule ...................................................................................................... 32

4.1 Resources ..................................................................................................................... 32

4.2 Staffing and Training Needs ........................................................................................ 32

4.3 Schedule ....................................................................................................................... 32

TPC_TRR_F15a_T07_V2.2.docx v

Table of Tables

Table 1: Test Case Overview and Mapping to Use Cases and Win Conditions

Table 2: TC-UI-01-01 Vendor can register for an account’

Table 3: TC-UI-01-02 Data from the Search Function

Table 4: TC-UI-02-01 Data Integration from API connection

Table 5: TC-UI-02-02 Validity of Search Result Data

Table 6: TC-UI-03-01 Check Search Module performance

Table 7: TC-L-01-01 Correctness of displaying filters

Table 8: TC-L-02-01 Data integration from the Petfinder API

Table 9: TC-L-03-01 Clicks’ timing

Table 10: TC-L-03-02 Clarity of the UI and satisfaction with it.

Table 11: TC-L-03-03 UI on other versions of Android

Table 12: TC-G-01-01 Display correct Map Address in Google Map

Table 13: TC-G-02-01: Correctness in shelter page UI

Table 14: TC-G-03-01: Check Shelter information from Petfinder

Table 15: TC-I-01-01 Test search action redirecting to list view

Table 16: TC-I-01-02 Check search criteria is satisfied

Table 17: TC-I-01-03 list view redirection is timely

Table 18: TC-I-01-04 Check thumbnail images exist and are correct

Table 19: TC-I-01-05 Check clicking list item redirects to detail page

Table 20: TC-AU-01-01 Login

Table 21: TC-AU-01-02 Password


vi

Table 22: TC-AU-01-03 Email

Table 23: TC-AU-01-04 Integration

Table 24: TC-AU-01-05 Boundary Conditions

Table 25: TC-A-01-01 Intent thread connection check

Table 26: TC-A-01-02 Custom built automated mail

Table 27: TC-A-02-01 load Balance Check


7

1. Introduction

The purpose of testing for this project is to verify that the Android Application that was

chosen, implemented and configured provides the needed functionality of the client. The

scope of testing is based on the use cases developed to meet the needed functionality.

Since the software was developed by the project team, testing is focused on errors in

coding or overall performance metrics and functionality.

The types of test cases that have been developed are software item and functionality test.

Due to the size and scope of requirements, we have attempted to test the functionality that

delivers the “Must have” capabilities, while deferring other Should, Could and Want

capabilities to another phase, or for future development by the client.


8

2. Test Strategy and Preparation

The overall project test strategy will be to prioritize tests according to client requirements

– i.e. value-based test. As higher priority items are completed and tested, next level

priority items will be addressed and tested.

All development testing will be conducted against the prototype, that was provided by the

Client All tests were created to test individual use cases, and demonstrate required

capability. Therefore, all tests can be traced back to Use Case scenarios along with Win

Conditions, either directly, or inferred.

2.1 Hardware preparation

The prototype was provided by the client during a client interaction meeting and all

functional testing will be against the prototype. No additional hardware is necessary

other than the ones used for the development cycle.

After migration to the clients’ server, if time permits, non-functional testing will be

performed. Software preparation

The prototype is currently populated with test data from PETFINDER API, and will be

used as is for testing functionality. No additional software or test simulators will be used.

After client provides with the additional shelter details, functional testing will validate

successful transfer, using test data prior to implementation.

Any additional functionality that is implemented after the system is delivered will not be

tested as part of the CSCI 577a project.

2.2 Other pre-test preparations

No other pre-test preparations are needed.


9

2.3 Requirements Traceability

Table 1: Test Case Overview and Mapping to Use Cases and Win Conditions

Test Case Test

Description

Sub Test

Case Sub Test Case Description

Requirement

Traceability

(WinBook)

TC-UI-01 Search Function TC-UI-01-01 User Search WC_3962

TC-UI-01-02 Data from Search function WC_3962

TC-UI-02-01 Data Integration from API

connection WC_4066

TC-UI-02-02 Validity of Search Result

Data WC_4066

TC-UI-03

Search

functionality

Performance TC-UI-03-01

Check Search module

performance WC_4066

TC-L-01 Displaying a list

of pets TC-L-01-01

Correctness of displaying

filters WC_4066

TC-L-02

Detailed

information of

fetched

TC-L-02-01 Data integration from API WC_4052

TC-L-03 Traverse fetched

Data TC-L-03-01 Click Timings WC_4055

TC-L-03-02 Clarity of the UI and

satisfaction with it WC_3962

TC-L-03-03 UI on other versions of

Android

WC_4052

WC_4052

TC-G-01 Google Map TC-G-01-01 Google Map Address WC_4053

TC-G-02 Shelter UI TC-G-02-01 Correctness in shelter UI WC_4055

TC-G-03 Check shelter

information TC-G-03-01

Check Shelter information

from Petfinder WC_4026

TC-I-01 Fuppy Search TC-I-01-01 Functionality Testing WC_4038

TC-I-01-02 Test Redirection WC_4038

TC-I-01-03 List View WC_4038

TC-I-01-04 Thumbnail WC_4038

TC-I-01-05 List Redirection WC_4038

TC-AU-01 Fuppy

Authentication TC-AU-01-01 Login WC_4062

TC-AU-01-02 Password WC_4062 TC-AU-01-03 Email WC_4062 TC-AU-01-04 Integration WC_4062 TC-AU-01-05 Boundary conditions WC_4062


10

Test Case Test

Description

Sub Test

Case Sub Test Case Description

Requirement

Traceability

(WinBook)

TC-A-01 Appointment

System TC-A-01-01

Intent thread connection

check WC_4038

TC-A-01-02 Custom built automated mail WC_4038

TC-A-02 Application

Performance TC-A-02-01 Load Balance

WC_4008

WC_4038

3. Test Identification

Table 1 provides a high-level overview of the various tests that have been defined for the

system. The following section provides more detail on the tests, and completion, pass

and fail criteria.

3.1 TC-UI-01 Search Function 3.1.1 Test Level

Unit Testing

3.1.2 Test Class

UI Testing, Data Testing

3.1.3 Test Completion Criteria

Working of the search functionality


11

3.1.4 Test Cases

Table 2: TC-UI-01-01 Vendor can register for an account

Test case Number TC-UI-01-01 Basic Search UI Function

Test Item Check the frontend for the Search Functionality and see if it works

properly before integrating it with the API. Check to see if all the

dropdown menu displays correct data and are properly aligned.

Test Priority M - Must have

Pre-conditions N/A

Post-conditions Test to get data selected by the user

Input Specifications No input data required

Expected Output

Specifications

All drop-down menus should have proper data in the list. The UI

elements should be properly aligned and should be functional.

Pass/Fail Criteria Correct data display in drop-down menus and proper

alignment of UI elements

Assumptions and

Constraints

N/A

Dependencies N/A

Traceability Win Condition (WC_3962) As a user, I want to use a simple and

clear UI, so that I could know how to operate


12

Table 3: TC-UI-01-02 Data from the Search Function

Test to see if the values selected or entered by the user from the drop-down

menus and textbox are submitted properly when user clicks search

Test case Number TC-UI-01-02 Data from the Search Function

Test Item Check that the values which have been selected or entered by the

users are the values which are being submitted on button click.

Check to see if all the dropdown menu have a default value in case

the user forgets to select the value.


Pre-conditions N/A

Post-conditions Establish Integration to API to retrieve contact details of shelters.

Input Specifications User inputs

Expected Output

Specifications

The data submitted should be the data selected from the drop-down

menu and textbox.

Pass/Fail Criteria The data submitted is same as the data selected or entered by the user

Assumptions and

Constraints

N/A

Dependencies N/A

Traceability Win Condition (WC_3962) As a user, I want to use a simple and clear

UI, so that I could easily know how to operate


13

3.2 TC-UI-02 Data from Petfinder API 3.2.1 Test Level

Integration Testing

3.2.2 Test Class

Input Testing & Data Integration testing


Pet information fetched from the API

3.2.4 Test Cases

Table 4: TC-UI-02-01 Data Integration from API connection

Test using the data retrieved from the Pet finder API and check results

Test case Number TC-UI-02-01 Data Integration from API connection

Test Item Integrate the Pet finder API with the Search UI Elements

Test Priority M-Must have

Pre-conditions Established successful API connection.

Post-conditions Check the results displayed

Input Specifications Data from the Pet find API

Expected Output Search functionality without the filter is established

Specifications

Pass/Fail Criteria Pet data should be retrieved

Assumptions and Assumed that Connection already established to pet

Constraints finder

Dependencies Connection established using Pet finder API

Traceability Win Condition (WC_4066)

As a user I want to apply type/locations/price etc filters

on search results sorted so that I can have more accurate

results.


14

Table 5: TC-UI-02-02 Validity of Search Result Data

Test using the data retrieved from the Pet finder API and check if the results

displayed are according to the user selection

Test case Number TC-UI-02-02 Validity of Search Result Data

Test Item When the users clicks on search button check whether the

data obtained from the Pet finder API is according to the

user selected.

Test Priority M-Must have

Pre-conditions Able to retrieve data from Pet finder

Post-conditions Check Pet Detail Information

Input Specifications Data from the Pet find API and data from user input

Expected Output Basic search functionality has been established

Specifications

Pass/Fail Criteria Pet data retrieved should be according to the user

selection

Assumptions and Assumed that Connection already established to pet finder

Constraints

Dependencies Data Integration from Pet finder


As a user I want to apply type/locations/price etc filters


results.

3.3 TC-UI-03 Search functionality performance 3.3.1 Test Level

System Testing

3.3.2 Test Class

Input Testing, Data Integration Testing, Validation and verification


15


Working of the search function

3.3.4 Test Cases

Table 6: TC-UI-03-01 Check Search Module performance

Test overall performance of the search module

Test case Number TC-UI-03-01 Check Search Module Performance

Test Item Check the overall search module performance

Test Priority M- Must Have

Pre-conditions Individual unit testing

Post-conditions N/A

Input Specifications Test everything required for search function

Expected Output Function working as per the clients’ request

Specifications

Pass/Fail Criteria Test cases passed without errors

Assumptions and Assumed that all unit test cases are passed and user

Constraints knows how to use an Android Phone

Dependencies N/A


As a user I want to apply type/locations/price etc filters on

search results sorted so that I can have more accurate

results.

3.4 TC-L-01 Displaying a list of pets 3.4.1 Test Level

Unit testing

3.4.2 Test Class

Erroneous output testing


16


Every pet listed in the pets’ detailed page has to have the filters applied in the search page

3.4.4 Test Cases

Table 7: TC-L-01-01 Correctness of displaying filters

Test if the filters submitted from the search page match the filters appearing in the list of

pets

Test Case

Number

TC-L-01 Displaying a list of pets

Test Item Check if the filters submitted from the search page match the

filters displayed for each pet

Test Priority M

Pre-Conditions Search page filters applied

Post-Conditions Compare filters displayed with the ones selected

Input

Specifications

User selects filters on the search page

Expected

Output

Specifications

User sees filters he selected on every pet's high level description

Pass/Fail

Criteria

The filters selected match the filters displayed (pass), some of the

filters match (fail), none of the filters match (fail)

Assumptions

and Constraints

----

Dependencies Search page form submitted

Traceability WC_4066: As a user I want to apply type/locations/price etc filters

on search results sorted so that I can have more accurate results

3.5 TC-L-02 Detailed information from Petfinder 3.5.1 Test Level

Integration Testing

3.5.2 Test Class

Data test


Pet detailed information and pictures from Petfinder are correctly displayed


17

3.5.4 Test Cases

Table 8: TC-L-02-01 Data integration from the Petfinder API

Test if the data given from Petfinder are the same data displayed on the detailed page for

each pet

Test Case

Number

TC-L-02-01 Data integration from the Petfinder API

Test Item Integrate petfinder data correctly in the detailed page for each pet

Test Priority M

Pre-Conditions Select a specific pet, set up connection with API

Post-Conditions Compare displayed detailed information with data from Petfinder

Input

Specifications

Data (including pictures) from Petfinder

Expected

Output

Specifications

User sees all the data in each page

Pass/Fail

Criteria

The data match the petfinder data (pass), some of the data match

(fail), none of the data match (fail)

Assumptions

and Constraints

Petfinder API works correctly

Dependencies Displaying a list of pets

Traceability WC_4052: As a User, I should be able to see pet's information, so

that I can decide whether I should go and see the pet or not

3.6 TC-L-03 Traverse Fetched Data 3.6.1 Test Level

Acceptance Testing

3.6.2 Test Class

Timing testing, Alpha testing, UI testing


The test will be completed when the system displays all orders for the account that is

accessing the system.


18

3.6.4 Test Cases

Table 9: TC-L-03-01 Clicks’ timing

Test if the click of each button gives a response of less than 1 second

Test Case

Number

TC-L-03-01 Clicks’ timing

Test Item End user gets a result after clicking on a button (for selecting pet,

switching pictures or visiting shelter) in less than 1 second

Test Priority S

Pre-Conditions User clicks on one of the three buttons specified above

Post-Conditions User gets a response in less than 1 second

Input

Specifications

----

Expected

Output

Specifications

----

Pass/Fail

Criteria

Response time less or equal than 1 second (pass), response time

greater than 1 second (fail), app crashes or shuts down (fail)

Assumptions

and Constraints

Petfinder API and Android machine do not crash

Dependencies ----

Traceability WC_4055: As a user, I should be able to see the pets' pictures

quickly so that I do not have to wait.

Table 10: TC-L-03-02 Clarity of the UI and satisfaction with it

Test the user’s satisfaction on the details page and UI clarity

Test Case

Number

TC-L-03-02 Clarity of the UI and satisfaction with it

Test Item End user can easily navigate through high-level pet descriptions, is

satisfied with how data is displayed in the detailed descriptions

Test Priority S

Pre-Conditions End user navigates through the pet details page

Post-Conditions ----

Input

Specifications

Excel sheet with scores 1-5 for high level descriptions and 1-5 for

detailed descriptions

Expected

Output

Specifications

Table of scores


19

Pass/Fail

Criteria

Score of 4 or 5 (pass), score of 3 (pass and will fix), score of 1 or 2

(fail)

Assumptions

and Constraints

Alpha testing, nonbiased testing

Dependencies Displaying list of pets

Traceability WC_4052: As a User, I should be able to see pet's information, so

that I can decide whether I should go and see the pet or not WC_ 3962: As a user, I want to use a simple and clear UI, so that I

could easily know how to operate

Table 11: TC-L-03-03 UI on other versions of Android

Test if the UI works correctly on all the versions of Android past the Kitkat

version

Test Case Number TC-L-03-03 UI on other versions of Android

Test Item The UI works correctly on different versions of Android

Test Priority S

Pre-Conditions Open application in different versions of Android

Post-Conditions Compare list spacing, font, picture size

Input

Specifications

----

Expected Output

Specifications

----

Pass/Fail Criteria Text is not overlapping and data is slightly separated (pass),

overlapping text (fail), different fonts (fail)

Assumptions and

Constraints

All the Android versions after Kitkat available to us

Dependencies ----

Traceability WC_ 3962: As a user, I want to use a simple and clear UI, so

that I could easily know how to operate

3.7 TC-G-01 Display correct address in google map 3.7.1 Test Level

Unit test item


20

3.7.2 Test Class

Erroneous test


Show correct map address according longitude and Latitude on Google Map Test Cases

Table 12: TC-G-01-01 Display correct Map Address in Google Map

Test Case Number TC-G-01: Display correct Map Address in Google

Map

Test Item find map address on google map.

Test priority User should find address on Google Map.

Pre-condition As a user, I can access to search pet, then select favorite

pet.

Post -conditions Click visit shelter and open shelter information page to

find map address on google map.

Input specification Select pet and click visit shelter.

Expected output

specification

Show Address on Map.

Not Show Address on Map

Pass/fail criteria Pass / Show Address on Map.

Fail/ Not Show Address on Map

Assumption and

constraints

First search pets, and select favorite pet.

Dependencies Search functionality, pet detail page

Tractability As a user I want to apply type/locations/price etc. filters


results.

3.8 TC-G-02 Correctness in Shelter Page UI 3.8.1 Test Level

Software item

3.8.2 Test Class

Erroneous test


21


User can see shelter page easily without any problem in UI.

3.8.4 Test Cases

Table 13: TC-G-02-01: Correctness in shelter page UI

Test Case Number TC-G-01: Correctness in shelter page UI.

Test Item Easily open shelter page without any problem to show.

Test priority User should open shelter page easily.


pet.

Post -conditions Click visit shelter and open shelter information page.

Input specification Select pet and click visit shelter.

Expected output

specification

Show Shelter page without problem in UI.

Show Shelter page with problem in UI.

Pass/fail criteria Pass / Show Shelter page without problem in UI.

Fail /Show Shelter page with problem in UI.

Assumption and

constraints

First search pets, and select favorite pet.

Dependencies Search functionality, pet detail page

Traceability As a user, I want to use a simple and clear UI, so that I

could easily know how to operate

3.9 TC-G-03 Check Shelter information 3.9.1 Test Level

Data test item

3.9.2 Test Class

Erroneous test


22


Show correctness of Shelter information include shelter name, phone, email, address

from Petfinder.

3.9.4 Test Cases

Table 14: TC-G-03-01: Check Shelter information from Petfinder

Test Case Number TC-G-03-01: Check Shelter information from

Petfinder.

Test Item Shelter information show correct data from Petfinder

API.

Test priority User should see correct data in shelter page.


pet with connection Data of Petfinder.

Post -conditions Click visit shelter and open shelter information page to

find correct data of Petfinder.

Input specification Select pet with ID and click visit shelter with Shelter ID.

Expected output

specification

Show correct information in shelter page from Data

Petfinder/Not correct data.

Pass/fail criteria Pass / Show correct information from Data of Petfinder.

Fail/ Not correct data.

Assumption and

constraints

Petfinder API connection with App show correct data.

Dependencies Search functionality, pet detail page.

Tractability As a user I want to apply type/locations/price etc. filters


results.

3.10 TC-I-01 Fuppy Search Functionality 3.10.1 Test Level

System Testing

3.10.2 Test Class

Erroneous test


23


The test suite will be completed when

- The test suite is run as part of the quality assurance measure

- Every test case passes and shows up green

3.10.4 Test Cases

Table 15: TC-I-01-01 Test search action redirecting to list view

Test Case Number TC-I-01-01 test search action redirecting to list view

Test Item Search page and user input widgets

Test Priority Must have

Pre-conditions The application is at the search page

Post-conditions The application is at list view with list of pets displayed

on screen

Input Specifications press search button

Expected Output

Specifications

Pets should be displayed on screen

Pass/Fail Criteria -pass: redirection to list view, pets information populated

-fail: did not redirect; list view is empty when non-empty

result expected

Assumptions and

Constraints

Application is connected to internet and API end point is

working

Dependencies Petfinder API is available

Traceability Search should return results

This is a basic functional test to make sure that users can filter result based on criteria

they entered

Table 16: TC-I-01-02 Check search criteria is satisfied

Test Case Number TC-I-01-02 Check search criteria is satisfied

Test Item Pets in list view and search criteria




on screen

Input Specifications Select appropriate spinner value and press search

Expected Output

Specifications

Pets displayed on screen satisfy search criteria


24

Pass/Fail Criteria -pass: all of the pets in list view satisfy search criteria

-fail: any of the pets in list view does not satisfy search

criteria

Assumptions and

Constraints

Application is connected to internet and API end point is

working

Dependencies Petfinder API is available


This is a usability test to make sure that the application is performing efficiently. A

latency too long usually indicates a poor implementation and would cause users to suffer

from waiting

Table 17: TC-I-01-03 list view redirection is timely

Test Case Number TC-I-01-03 list view redirection should be within 3

seconds

Test Item List view

Test Priority Should have



on screen

Input Specifications Select appropriate spinner value and press search

Expected Output

Specifications

Pets are displayed on screen within 3 seconds

Pass/Fail Criteria -pass: redirection to list view within 3 seconds

-fail: redirection takes more than 3 seconds or doesn’t

redirect

Assumptions and

Constraints

Application is connected to fast internet and API end point

is working

Dependencies Petfinder API is available and satisfies Service Level

Agreement


This is a usability test to make sure media elements should not be ignored. Images

contribute great value to the application and thus should be tested

Table 18: TC-I-01-04 Check thumbnail images exist and are correct

Test Case Number TC-I-01-04 Check thumbnail images exist and are correct

Test Item List view thumbnail images

Test Priority Should have

Pre-conditions The application is at list view with list of pets displayed

on screen


on screen

Input Specifications None


25

Expected Output

Specifications

List view is populated with pets thumbnail images

Pass/Fail Criteria -pass: thumbnail image correspond to the pet shown

-fail: thumbnail image is not loaded or is wrong

Assumptions and

Constraints

Petfinder has correct link for pet images

Dependencies Petfinder API, CDN

Traceability List view should correctly display pets information

This is a basic work-flow testing to ensure user can proceed with standard procedure

Table 19: TC-I-01-05 Check clicking list item redirects to detail page

Test Case Number TC-I-01-05 Check clicking list item redirects to detail

page

Test Item List view and details view


Pre-conditions The application is at list view with list of pets displayed

on screen

Post-conditions The application is at detail view with pet information

displayed on screen

Input Specifications User presses an item in list

Expected Output

Specifications

Detail view is populated with pet details

Pass/Fail Criteria -pass: detail view is populated with corrected pet details

-fail: detail view is empty or doesn’t redirect

Assumptions and

Constraints

Petfinder API is working

Dependencies Petfinder API

Traceability List view can direct to detail view

3.11 TC-AU-01 User Authentication 3.11.1 Test Level

Integration Testing

3.11.2 Test Class

Authentication functionality, including login and registration. And it is mainly erroneous

input testing


26


Consider all kinds of possible errors made by users as many as possible.

The function needs response correctly respects to different kind of errors.

MC/DC Criterion.

3.11.4 Test Cases

Description:

According to the input data in authentication, there are basic 3 types data, e-mail

as username, password, and confirm-password. Therefore, I need to test every type of

errors, such as null data errors, invalid username, not same password, not correct

password for this username and any others like these.

Table 20: TC-AU-01-01 Login

Test Case Number TC-AU-01-01

Test Item Username and password. At least one of them not input data, click login

directly

Test Priority S

Pre-conditions NONE

Post-conditions Response none of the input data could be null

Input

Specifications

Lack one of input data, like username or password

Username: Password:

Username: aaa Password:

Username: Password: dadas

Expected Output

Specifications

cannot access authentication, response to users that they need to input all

required data

Pass/Fail Criteria Compare it with expected output to check whether it pass or fail

Assumptions and

Constraints

User forget to input some data to login.

Dependencies This test case must be execute prior to TC-AU-02 and TC-AU-03 and

TC-AU-04

Traceability WC_4062:As a user I want my information to be kept secure so that it

cannot be misused.

Description:

For this test case, I am testing the boundary values for this classes, because username is

required as an email format. In addition, some users may not know or forget that

username’s requirement, so it is important for user to know where is error input.


27

Table 21: TC-AU-01-02 Password


Test Item Username. Invalid format username

Test Priority M

Pre-conditions NONE

Post-conditions Response input an invalid username

Input

Specifications

Input both username and password, but username are not an email

format

Username: aaa Password:123

Username: bbb@ss Password:123

Expected Output

Specifications

cannot access authentication, response to input an email format

username


Assumptions and

Constraints

User forget that the username requires an email format, and input wrong

username

Dependencies This test case must be execute prior to TC-AU-03 and TC-AU-04


cannot be misused.

Description:

For this test case, I am testing the boundary test for this group that username is not in the

database. Because, sometimes users may confuse what is the username have them

registered, so that it could be a response let users know these are not their username.

Table 22: TC-AU-01-03 Email


Test Item Username. No username in the database

Test Priority S

Pre-conditions This username has not been registered

Post-conditions Response this username not exist

Input

Specifications

Username and password are both correct format, but username not exist

in database

Username: [email protected] Password:123 But in database, there is not

username [email protected]

Expected Output

Specifications

cannot access authentication, response the username has not been

registered


Assumptions and

Constraints

User know the format of username, but maybe forget username or make

a typo on username

Dependencies This test case must be execute prior to TC-AU-04


cannot be misused.

mailto:[email protected]



28

Description:

For this test case, I am testing boundary value of incorrect password. This is important

because when user do not get access into system, they need to know what is wrong input,

password or username or something else. Table 23: TC-AU-01-04 Integration


Test Item Username, Password. Username and password are mismatching

Test Priority M

Pre-conditions Input correct username in database and mismatching password

Post-conditions Response password are not correct with respect to this username

Input

Specifications

Correct username, and password are mismatching with this username

Username: [email protected] Password:123 Actually, in database, for

username [email protected] password is 1234

Expected Output

Specifications

cannot access authentication, response not correct password to the

username


Assumptions and

Constraints

User make a typo on password or forget password

Dependencies NONE


cannot be misused.

Description:

For this test case, I am testing boundary values of user access system successfully. And it

is important that user should access system when input correct username and password.

Table 24: TC-AU-01-05 Boundary Conditions


Test Item Username, Password. Correct Username with matching password.

Access system through authentication successfully

Test Priority M

Pre-conditions This pair of username and password are exactly in database

Post-conditions Access system

Input

Specifications

Username and password are both in database and are matching

Input Username: [email protected] Password:123

Database Username :[email protected] Password:123

Expected Output

Specifications

Pass authentication and access system


Assumptions and

Constraints

Input both correct username and match able password

Dependencies NONE

http://bbb.cc/



http://bbb.cc/


29


cannot be misused.

3.12 TC-A-01 Appointment System 3.12.1 Test Level

Unit Testing

3.12.2 Test Class

Data Testing, Input Testing


Working of email push server

3.12.4 Test Cases

Table 1: TC-A-01-01 Intent thread connection check

Test to see if an alert can be sent to the shelter once the user finds interest in a pet. Part of

static analyses.

Test case Number TC-A-01-01 Intent thread connection check

Test Item Check the backend thread connection to the mail

server and push data through the built in client

mobile application


Pre-conditions N/A

Post-conditions Test to send a mail from automated mailing

system without the client application middleware

Input Specifications Ping sample data

Expected Output

Specifications

Receive back the ping sent as input

Pass/Fail Criteria Data fetched and receive reply authentication-

Pass

Assumptions and

Constraints

Assumptions that mail server uses open secure

connection. Load balancer constraints

Dependencies In built Android client mail application


30


As a user, I should be able to book, update or

cancel my appointment, so that I inform the

agencies.

Table 2: TC-A-01-02 Custom built automated mail

Test the custom communication module built within the system that

automatically sends the required mail directly from the native mobile

application without connecting to the mobile integrated mailing

application.

Test case Number TC-A-01-02 Custom built automated

mail

Test Item Test the created application specific

automated mail system

Test Priority W - Want to have

Pre-conditions Intent Thread Connection

Post-conditions Establish Integration to API to retrieve

contact details of shelters

Input Specifications Sample sender and receiver email id- test

data

Expected Output

Specifications

Sent mail confirmation.

Pass/Fail Criteria Test email sent to a sample mail id

directly from user application- Pass

Assumptions and

Constraints

Assumption-Connection already

established with the mail server

Dependencies N/A


As a user, I should be able to book, update or cancel my

appointment, so that I inform the agencies.


31

3.13 TC-A-02 Load Balance Check 3.13.1 Test Level

System performance level (level of service)

3.13.2 Test Class

Input Testing, Data Integration Testing, validation and verification


Email alert to data fetched from API

3.13.4 Test Cases

Table 5: TC-A-03-01 Check Load balance

Test overall performance of the system to validate all win conditions and see if

application can handle high load of data from API

Test case Number TC-A-03-01 Check Application Performance

Test Item Overall system performance

Test Priority M- Must Have

Pre-conditions Individual module testing

Post-conditions N/A

Input Specifications Test everything requested as win

conditions

Expected Output

Specifications

System working as per the clients’ request

Pass/Fail Criteria Test cases passed without errors

Assumptions and

Constraints

Assumption that all unit test cases are

passed. Assumption that the user knows

basic knowledge of android applications

Dependencies N/A


As a user, I should be able to book, update or

cancel my appointment, so that I inform the

agencies.


32

4. Resources and schedule

Testing resources are comprised of the NICE project team. During development of the

capability, testing is conducted by the developer to determine initial functionality.

After the capability has been determined to meet the required functionality, the QFP is

responsible for developing test procedures, conducting tests, and updating documentation

in the Test Procedures and User Manual.

The team has 1 Project manager, Requirements engineer,3 developers and 1 QFP.

The Application solution was not determined until after the Foundation Commitment

Review. Once an initial prototype was developed, test schedules were defined to

complete testing prior to the Transition to Readiness Review.

4.1 Resources

The prototype developed and was ready to be tested in a 4” screen android mobile with

minimum of KitKat installed.

4.2 Staffing and Training Needs

Ideally, all team members will conduct testing to validate system functionality and

performance. All team members have been validating functionality for their assigned

task, including creation of test data and executing tests on the prototype.

As the system is mostly JAVA, a basic knowledge of software systems, along with a

basic understanding of UI and API is necessary to conduct testing.

4.3 Schedule

Table 28: Testing Schedule

Date Test Identifier Responsible

person

Resources

11/13/16 TC-UI-01-01, TC-UI-01-

02, TC-UI-02-01, TC-UI-

02-02,

Fereshteh

Khorzani

Prototype and test data

11/15/16 TC-L-02-01, TC-L-01-01,

Fereshteh

Khorzani


11/20/16 TC-G-01-01, TC-G-03-01,

TC-G-02-01

Fereshteh

Khorzani



33

11/22/16 TC-I-01-01, TC-I-01-03,

TC-I-01-02, TC-I-01-04,

TC-I-01-05

Kevin Prototype, test data and payment test

gateway

11/27/16 TC-AU-01-01, TC-AU-01-

02, TC-AU-01-03, TC-AU-

01-04, TC-AU-01-05

Joseph Prototype and test data

11/29/16 TC-A-01,TC-A-01-02 Krupa Patel Prototype and test data

12/4/16 TC-L-02-01 Praveen chander Prototype and test data

12/6/16 TC-A-02-01 Praveen chander Prototype and test data

Documents

Test Plan and Cases (TPC) - University of Southern California · Test Plan and Cases (TPC) Fuppy Team No.7 Krupa Patel ... Post-conditions Establish Integration to API to retrieve