Post on 03-Apr-2020
SOFTWARE TEST DOCUMENT
Version 1.1
10.06.2013
MOBCOLL PROJECT
Prepared By: ANDIOS
Murat Öksüzer
Sercan Çidem
Vedat Şahin
Fatih Osman Seçmen
1
Change History
*A - ADDED M - MODIFIED D – DELETED
VERSION
NUMBER
DATE NUMBER OF
FIGURE,
TABLE OR
PARAGRAPH
A*
M
D
TITLE OF
BRIEF
DESCRIPTION
1.0 14.04.2013 Original
1.1 10.06.2013 2.2.14
2.2.20
2.2.21
2.2.22
4.2
A,
M,
View List of
Borrowed
Books, Share
his/her
information in
social media,
Recommend a
book to a
friend, Lend a
book to a friend
Traceability
Matrix is
modified
2
Preface
This Software Test Document is intended to provide guidance on the management of
Mobile Book Collector. The document has been tailored according to the “IEEE Standard for
Software and System Test Documentation – IEEE Std 829 – 2008”.
This Test Report provides a complete description of all the test cases of the Mobile
Book Collector Project.
The first section of this document includes problem definition, purpose, scope,
references and notation for description.
The second section of this document includes all the test types and test cases of the
Mobile Book Collector Project.
The third section of this document includes performance test strategy for Mobile Book
Collector Project.
The last section of this document includes glossary and traceability matrix.
3
Table of Contents
1. Introduction ......................................................................................................................................... 5
1.1. Problem Definition ....................................................................................................................... 5
1.2. Purpose ......................................................................................................................................... 5
1.3. Scope ............................................................................................................................................ 5
1.4. References .................................................................................................................................... 6
1.5. Notation we used for description ................................................................................................ 6
2. Mobile Book Collector Test Case Details ............................................................................................. 6
2.1 Functional Test Cases .................................................................................................................... 6
2.2.1 Register ................................................................................................................................... 6
2.2.2 Login ....................................................................................................................................... 7
2.2.3 Login with Facebook ............................................................................................................... 8
2.2.4 Logout ..................................................................................................................................... 8
2.2.5 Update User Profile ................................................................................................................ 9
2.2.6 Update Book Information ....................................................................................................... 9
2.2.7 Update a Book’s Category .................................................................................................... 10
2.2.8 Adding a Book into Category ................................................................................................ 11
2.2.9 Add Book with Scanning ISBN Number ................................................................................ 11
2.2.10 Add Book Manually ............................................................................................................ 12
2.2.11 Delete a Book ..................................................................................................................... 12
2.2.12 Add Cover of the Book from “Take a Photo” ..................................................................... 13
2.2.13 Add Cover of the Book from “Browse button” .................................................................. 14
2.2.14 View List of Owned Books .................................................................................................. 14
2.2.15 Search Current Book List .................................................................................................... 15
2.2.16 View List of Borrowed Books ............................................................................................ 15
2.2.17 Add a Friend ....................................................................................................................... 16
2.2.18 Delete a friend .................................................................................................................... 16
2.2.19 Manage Settings ................................................................................................................. 17
2.2.20 Share his/her information in social media ....................................................................... 17
2.2.21 Recommend a book to a friend ........................................................................................ 18
2.2.22 Lend a book to a friend ..................................................................................................... 18
2.2.23 View Profiles of his/her Friends ......................................................................................... 19
2.2.24 View User History ............................................................................................................... 20
4
2.2.25 View User History of a Friend ............................................................................................. 20
2.2.26 Help Menu .......................................................................................................................... 21
3. Performance Test Strategy ................................................................................................................ 21
3.1 Description .................................................................................................................................. 21
3.1 Performance Test ........................................................................................................................ 22
4. Global ................................................................................................................................................ 22
4.1. Glossary ...................................................................................................................................... 22
4.2. Traceability Matrix................................................................................................................. 23
5
1. Introduction
1.1. Problem Definition
People collecting items often had difficulty in keeping track of their collection
repository. Storage and location, availability, missing items, wanted items, borrowed items,
web and shopping searching are among tasks that a collector might need help. Also people
want to share their own books and library information with other people on social media and
these social features will be provided with this collector.
1.2. Purpose
This document is prepared for the specification of testing process of Mobile Book
Collector project. With the help of this testing document we are aiming to have our project
with the following quality criteria being satisfied.
- High performance
- Being error-free
- Logically correctness
- Compatibility between modules
- Easy-to-use
- Genuinely real-time
1.3. Scope
This document briefly describes the testing process of Mobile Book Collector project,
and this document gives a detailed description of all test cases and interface specifications.
This document shows and documents the tests types and test cases used to check the
software failures and their respective results.
In this document, we mainly focus on:
- What is going to be tested
- How to be assured that if the system is working as expected
- The testing strategies & procedures
- The functional and non-functional test results
6
1.4. References
IEEE STD 829-2008, IEEE Standard for Software and System Test Documentation
Mobile Book Collector Project - System Requirement Specification
Mobile Book Collector Project - Software Design Document
1.5. Notation we used for description
The structure and explanation of the part of test cases explained below.
- TC ID: This section explains the id of the test case with a number
- Use Case: This section explains the case number for use cases.
- Precondition: This section explains the environmental needs for running the test case like
what should be done before the running the test case.
- Steps: This section explains what is needed to be done to reach the expected results and what
is wanted to be done when the preconditions are provided in this test case.
- Expected Result: This section explains what is got after using the inputs.
- Success/ Fail: This section explains whether the expected result is reached or not.
2. Mobile Book Collector Test Case Details
2.1 Functional Test Cases
2.2.1 Register
TC ID TC_1
Use Case UC_1
Precondition 1. The application should be installed.
2. The RESTful web service should be running.
3. The user selects the sign up button in the welcome screen.
Steps 1. The system provides a list of boxes for user to enter the personal
information and a password.
7
2. The user fills the information gaps, and submits the form by touching
the “Sign Up” button.
Expected
Result
1. The system creates the user account and user successfully
registered.
2. The application returns the user to the login page.
Success / Fail Success
2.2.2 Login
TC ID TC_2
Use Case UC_2
Precondition 1. The application should be installed.
2. The RESTful web service should be running.
3. The user selects the login button in the welcome screen.
Steps 1. The system provides a list of boxes for user to enter his/her email
address and password.
2. The user fills the information gaps, and submits the form by touching
the “Login” button.
Expected
Result
1. The system sends the email address-password pair to the RESTful
web service and checks the database if the pair is valid.
2. The application directs user to the main page screen.
Success / Fail Success
8
2.2.3 Login with Facebook
TC ID TC_3
Use Case UC_2
Precondition 1. The application should be installed.
2. The RESTful web service should be running.
3. The user selects the “login with Facebook” button in the welcome
screen.
Steps 1. Facebook Login screen will show up.
2. The user fills up email and password information, presses login
button.
3. If user does not matches his/her application account with Facebook
account before, “registration page” comes to the screen whose name,
surname are filled.
4. The user fills new password and repeat password fields and press
“create account”.
Expected
Result
1. The user login with Facebook by using old or new account matching
with his/her Facebook account.
Success / Fail Success
2.2.4 Logout
TC ID TC_4
Use Case UC_3
Precondition 1. The application should be installed.
2. The RESTful web service should be running.
3. A user should have logged in to the system.
4. The user selects the logout button in the main page screen.
Steps 1. The system provides a logout button in the left menu.
2. The user touches the “Logout” button when s/he wants to close the
application.
9
Expected
Result
1. The application directs user to the welcome screen.
Success / Fail Success
2.2.5 Update User Profile
TC ID TC_5
Use Case UC_4
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views own profile by touching the “user profile” button.
3. The user touches the “edit” button on the bottom of the screen if s/he
wants to update any information about her/him.
Expected
Result
1. The system makes all text fields showing information about the user
editable.
Success / Fail Success
2.2.6 Update Book Information
TC ID TC_6
Use Case UC_4
Precondition 1. The user should have logged in to the system.
10
Steps 1. The system provides a menu on the left.
2. The user views owned books by touching the “my book list” button.
3. The user touches the “edit” button on the bottom of the screen if s/he
wants to update any information about the book selected from the list
on the left menu.
Expected
Result
1. The system makes all text fields showing information about the book
editable.
Success / Fail Success
2.2.7 Update a Book’s Category
TC ID TC_7
Use Case UC_4
Precondition 1. The user should have logged in to the system.
2. A book should have been added to a category before this test.
Steps 1. The system provides a menu on the left.
2. The user views owned books by touching the “my book list” button.
3. The user selects books from the list on the left menu by marking the
checkboxes near of each book after extending category list.
4. The user touches “add selected books into category” button.
Expected
Result
The system provides two choices to the user;
1. Adding into existing category showing the list of already created
categories.
2. Creating a new category.
Success / Fail Success
11
2.2.8 Adding a Book into Category
TC ID TC_8
Use Case UC_4
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views owned books by touching the “my book list” button.
3. The user selects books from the list on the left menu by marking the
checkboxes near of each book after extending “not categorized” list.
4. The user touches “add selected books into category” button.
Expected
Result
The system provides two choices to the user;
1. Adding into existing category showing the list of already created
categories.
2. Creating a new category.
Success / Fail Success
2.2.9 Add Book with Scanning ISBN Number
TC ID TC_9
Use Case UC_5
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views owned books by touching the “Add New Book”
button.
3. The user touches “Update Information with ISBN” button.
4. The user touches “Save Book” button on the right top screen to add the
book.
Expected 1. The system searched the scanned ISBN number on internet and filled
some text fields on the screen including ISBN, title, author,
12
Result publisher, publish date, language, type.
2. The system added the book to the user and it have been observed in
our local database.
Success / Fail Success
2.2.10 Add Book Manually
TC ID TC_10
Use Case UC_5
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views owned books by touching the “Add New Book”
button.
3. The user fills text fields on the screen s/he wanted to add.
4. The user touches “Save Book” button on the right top screen.
Expected
Result
1. The system added the book to the user and it have been observed in
our local database.
Success / Fail Success
2.2.11 Delete a Book
TC ID TC_11
Use Case UC_6
Precondition 1. User must login the application successfully
2. The user touches “My Book List” page from left menu.
13
Steps 1. The system provides a list of books from the left menu.
2. The user should mark the book that is wanted to be deleted.
3. The user can delete the selected books from “delete” button.
4. The confirmation dialog will pop up and wait the response of user.
5. User touches OK button.
Expected
Result
1. Selected books are deleted by the user.
Success / Fail Success
2.2.12 Add Cover of the Book from “Take a Photo”
TC ID TC_12
Use Case UC_7
Precondition 1. The user must login the application successfully
2. The user touches “Add Book” page from left menu.
or
3. The user touches “My Book List” page from left menü.
4. The user selects a book.
5. The user press “edit button”.
Steps 1. When “Take a Photo” is touched, the camera is started and waits for
user to take the book's photo.
2. The user takes a photo of book which you want to add.
3. After filling other information of the book, the user press “Save
Book” button.
Expected
Result
1. Cover of book is added.
Success / Fail Success
14
2.2.13 Add Cover of the Book from “Browse button”
TC ID TC_13
Use Case UC_7
Precondition 1. The user must login the application successfully
2. The user touches “Add Book” page from left menu.
or
3. The user touches “My Book List” page from left menu.
4. The user selects a book.
5. The user press “edit button”.
Steps 1. When “Browse” is touched, the application accesses to the device's
memory
2. Waits for user to select a picture file that will be added for book's
cover in database.
3. The user selects a picture.
4. After filling other information of the book, the user press “Save
Book” button.
Expected
Result
1. Cover of book is added.
Success / Fail Success
2.2.14 View List of Owned Books
TC ID TC_14
Use Case UC_8
Precondition 1. User should be in main page.
Steps 1. The user touches “my book list” button from left menu.
2. The user views list of owned books in the left menu.
3. The user can browse the books according to categories.
4. The application lists the information of a book selected from the
15
left menu.
Expected
Result
1. The user views list of owned books on the system.
Success / Fail Success
2.2.15 Search Current Book List
TC ID TC_15
Use Case UC_9
Precondition 1. User should be in “my book list” page.
Steps 1. User touches “search book” button.
2. User checks the wanted search categories.
3. User fills in the keywords for categories that is checked.
4. User touches the “search book” button.
Expected Result 1. Found books are listed as result of the search.
Success / Fail Success
2.2.16 View List of Borrowed Books
TC ID TC_16
Use Case UC_10
Precondition 1. User should be in “Book Market” page.
16
Steps 1. User touches “Borrowed books” button.
2. The user views list of borrowed books in the left menu
3. The user can browse the books according to categories.
4. The application lists the information of a book selected from the left
menu.
Expected
Result
1.The user views list of borrowed books on the system.
Success / Fail Success
2.2.17 Add a Friend
TC ID TC_17
Use Case UC_11
Precondition 1. User should be in “view profiles” page.
Steps 1. User selects a friend from the list.
2. User touches “add friend” button.
Expected Result 1. The user adds a friend to his/her friend list.
Success / Fail Success
2.2.18 Delete a friend
TC ID TC_18
Use Case UC_12
17
Precondition 1. User should be in “view friends” page.
Steps 1. User selects a friend from the list.
2. User touches “delete friend” button.
Expected Result 1. The user deletes a friend from his/her friend list.
Success / Fail Success
2.2.19 Manage Settings
TC ID TC_19
Use Case UC_13
Precondition 1. User should be in main page.
Steps 1. User touches the “settings” button placed on the left menu.
2. User updates the privacy settings.
3. User touches the “save” button and quits the settings.
Expected Result 1. The user changes the account privacy settings.
Success / Fail Success
2.2.20 Share his/her information in social media
TC ID TC_20
Use Case UC_14
Precondition 1. User may be in “My Book List” or “Add Book” page.
18
Steps 1. In “My Book List” page, user checks books to share.
2. The user touches facebook “share” button.
3. In “Add Book” page, when “Save Book” button clicked, a
confirmation dialog is shown whether user wants to share on facebook
or not.
4. If user confirms, the newly added book is shared on facebook.
Expected
Result
1.The book information is shared on facebook.
Success / Fail Success
2.2.21 Recommend a book to a friend
TC ID TC_21
Use Case UC_15
Precondition 1. User should be in “My Book List” page.
Steps 1. User selects a book from the book list on the left.
2. User touches the “Recommend” button.
3. User friend list is shown to choose friend that user wants to
recommend.
4. An input dialog is shown to user in order to leave extra message.
Expected
Result
1. A message about the recommendation is sent to selected friend.
Success / Fail Success
2.2.22 Lend a book to a friend
TC ID TC_22
19
Use Case UC_16
Precondition 1. User should be in “My Book List” page.
Steps 1. User selects a book from the book list on the left.
2. User touches the “Lend” button.
3. User friend list is shown to choose friend that user wants to
recommend.
4. An input dialog is shown to user in order to leave extra message.
Expected
Result
1. A message about the lending is sent to selected friend.
Success / Fail Success
2.2.23 View Profiles of his/her Friends
TC ID TC_23
Use Case UC_17
Precondition 1. User should be in main page.
Steps 1. On “user profile” page, there will be a “view friends” button.
2. The user chooses a friend from one of the user lists that comes by
touching the “view friends” button.
Expected
Result
1. The user profile information of selected friend is shown.
Success / Fail Success
20
2.2.24 View User History
TC ID TC_24
Use Case UC_18
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views history of his/her activities by touching the “View
History” button.
Expected
Result
1. The system lists the activities of user.
Success / Fail Success
2.2.25 View User History of a Friend
TC ID TC_25
Use Case UC_18
Precondition 1. User should be logged in to the application.
Steps 1. The user selects a friend or any other user allowing him/her profile
can be browsed.
2. The user touches the “view user history” button.
3. The transaction history of the user is displayed on the screen.
Expected
Result
1. User sees the history of other users who allow their history to be
shown by other users.
21
Success / Fail Success
2.2.26 Help Menu
TC ID TC_26
Use Case UC_19
Precondition 1. The user should have logged in to the system.
Steps 1. The system provides a menu on the left.
2. The user views information about already shown screen by touching
the “info” button on the right top screen.
Expected
Result
1. The system shows a short information about the screen. This facility
is valid in all screens.
Success / Fail Success
3. Performance Test Strategy
3.1 Description
Hardware and software system used during test:
Hardware
- Asus Laptop – Intel Core i5 CPU, 2.4 Ghz, 4GB RAM, 250GB HD, Resolution (1366*768),
Windows 7.
- Samsung Galaxy Tab 2, NVIDIA Tegra Dual Core, 1 Ghz, 512 MB RAM, Resolution (800-
1280), PowerVR SGX540 Graphic Card.
22
Software
- MYSQL 5.
- Eclipse IDE.
- Android with version 3.0 in emulator and 4.02 in Samsung Tab 2
- Apache Tomcat 7.
- Apache JMeter
3.1 Performance Test
- Android application user interface should response user actions that require web service
communication, in less than one minute.
- Our RESTful web service should response 1000 user requests simultaneously. This test will
be done by using Apache JMeter.
- The system was tested by four users simultaneously and no system crash was occurred.
4. Global
4.1. Glossary
Term Definition
Software Design Description
A document that completely describes all of
functions of a proposed system and the constraints
under which it must operate.
System Requirements
Specification
A document that completely describes all of the
functions of a proposed system and the constraints
under which it must operate. For example, this
document. (System Requirements Specification)
Software Test Document A document that detailing a systematic approach to
testing a system such as a machine or software.
ISBN The International Standard Book Number (ISBN) is
a unique numeric commercial book identifier.
23
IEEE
The Institute of Electrical and Electronics Engineers
(IEEE) is a professional association headquartered
in New York City that is dedicated to advancing
technological innovation and excellence.
RESTful
An approach for getting information content from a
Web site by reading a designed Web page that
contains an XML.
Eclipse IDE A multi-language software development environment
Android A mobile device operating system developed by
Google Inc.
Tomcat An application server from the Apache Software
Foundation.
Apache JMeter A desktop application that is designed to load test
functional behavior and measure performance.
4.2. Traceability Matrix
Use Cases:
Requireme
nts from
SRS
UC1
UC2
UC3
UC4
UC5
UC6
UC7
UC8
UC9
UC10
UC11
UC12
UC13
UC14
UC15
UC16
UC17
UC18
UC19
TC_1 X
TC_2 X
TC_3 X
TC_4 X
TC_5 X
TC_6 X
TC_7 X
24
TC_8 X
TC_9 X
TC_10 X
TC_11 X
TC_12 X
TC_13 X
TC_14 X
TC_15 X
TC_16 X
TC_17 X
TC_18 X
TC_19 X
TC_20 X
TC_21 X
TC_22 X
TC_23 X
TC_24 X
TC_25 X
TC_26 X