SOFTWARE TEST DOCUMENT Version MOBCOLL PROJECT

Transcription

1 SOFTWARE TEST DOCUMENT Version MOBCOLL PROJECT Prepared By: ANDIOS Murat Öksüzer Sercan Çidem Vedat Şahin Fatih Osman Seçmen

2 Change History *A - ADDED M - MODIFIED D DELETED VERSION NUMBER DATE NUMBER OF FIGURE, TABLE OR PARAGRAPH A* M D TITLE OF BRIEF DESCRIPTION Original A, View List of Borrowed Books, Share his/her information in social media, Recommend a book to a friend, Lend a book to a friend 4.2 M, Traceability Matrix is modified 1

3 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 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. 2

4 Table of Contents 1. Introduction Problem Definition Purpose Scope References Notation we used for description Mobile Book Collector Test Case Details Functional Test Cases Register Login Login with Facebook Logout Update User Profile Update Book Information Update a Book s Category Adding a Book into Category Add Book with Scanning ISBN Number Add Book Manually Delete a Book Add Cover of the Book from Take a Photo Add Cover of the Book from Browse button View List of Owned Books Search Current Book List View List of Borrowed Books Add a Friend Delete a friend Manage Settings Share his/her information in social media Recommend a book to a friend Lend a book to a friend View Profiles of his/her Friends View User History

5 View User History of a Friend Help Menu Performance Test Strategy Description Performance Test Global Glossary Traceability Matrix

6 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 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 5

7 1.4. References IEEE STD , 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. - : This section explains the id of the test case with a number - : This section explains the case number for use cases. - : This section explains the environmental needs for running the test case like what should be done before the running the test case. - : 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. - : This section explains what is got after using the inputs. - / Fail: This section explains whether the expected result is reached or not. 2. Mobile Book Collector Test Case Details 2.1 Functional Test Cases Register TC_1 _1 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. 1. The system provides a list of boxes for user to enter the personal information and a password. 6

8 2. The user fills the information gaps, and submits the form by touching the Sign Up button. 1. The system creates the user account and user successfully registered. 2. The application returns the user to the login page. / Fail Login TC_2 _2 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. 1. The system provides a list of boxes for user to enter his/her address and password. 2. The user fills the information gaps, and submits the form by touching the Login button. 1. The system sends the 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. / Fail 7

9 2.2.3 Login with Facebook TC_3 _2 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. 1. Facebook Login screen will show up. 2. The user fills up 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. 1. The user login with Facebook by using old or new account matching with his/her Facebook account. / Fail Logout TC_4 _3 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. 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. 8

10 1. The application directs user to the welcome screen. / Fail Update User Profile TC_5 _4 1. The user should have logged in to the system. 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. 1. The system makes all text fields showing information about the user editable. / Fail Update Book Information TC_6 _4 1. The user should have logged in to the system. 9

11 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. 1. The system makes all text fields showing information about the book editable. / Fail Update a Book s Category TC_7 _4 1. The user should have logged in to the system. 2. A book should have been added to a category before this test. 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. 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. / Fail 10

12 2.2.8 Adding a Book into Category TC_8 _4 1. The user should have logged in to the system. 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. 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. / Fail Add Book with Scanning ISBN Number TC_9 _5 1. The user should have logged in to the system. 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. 1. The system searched the scanned ISBN number on internet and filled some text fields on the screen including ISBN, title, author, 11

13 publisher, publish date, language, type. 2. The system added the book to the user and it have been observed in our local database. / Fail Add Book Manually TC_10 _5 1. The user should have logged in to the system. 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. 1. The system added the book to the user and it have been observed in our local database. / Fail Delete a Book TC_11 _6 1. User must login the application successfully 2. The user touches My Book List page from left menu. 12

14 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. 1. Selected books are deleted by the user. / Fail Add Cover of the Book from Take a Photo TC_12 _7 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. 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. 1. Cover of book is added. / Fail 13

15 Add Cover of the Book from Browse button TC_13 _7 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. 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. 1. Cover of book is added. / Fail View List of Owned Books TC_14 _8 1. User should be in main page. 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 14

16 left menu. 1. The user views list of owned books on the system. / Fail Search Current Book List TC_15 _9 1. User should be in my book list page. 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. 1. Found books are listed as result of the search. / Fail View List of Borrowed Books TC_16 _10 1. User should be in Book Market page. 15

17 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. 1.The user views list of borrowed books on the system. / Fail Add a Friend TC_17 _11 1. User should be in view profiles page. 1. User selects a friend from the list. 2. User touches add friend button. 1. The user adds a friend to his/her friend list. / Fail Delete a friend TC_18 _12 16

18 1. User should be in view friends page. 1. User selects a friend from the list. 2. User touches delete friend button. 1. The user deletes a friend from his/her friend list. / Fail Manage Settings TC_19 _13 1. User should be in main page. 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. 1. The user changes the account privacy settings. / Fail Share his/her information in social media TC_20 _14 1. User may be in My Book List or Add Book page. 17

19 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. 1.The book information is shared on facebook. / Fail Recommend a book to a friend TC_21 _15 1. User should be in My Book List page. 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. 1. A message about the recommendation is sent to selected friend. / Fail Lend a book to a friend TC_22 18

20 _16 1. User should be in My Book List page. 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. 1. A message about the lending is sent to selected friend. / Fail View Profiles of his/her Friends TC_23 _17 1. User should be in main page. 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. 1. The user profile information of selected friend is shown. / Fail 19

21 View User History TC_24 _18 1. The user should have logged in to the system. 1. The system provides a menu on the left. 2. The user views history of his/her activities by touching the View History button. 1. The system lists the activities of user. / Fail View User History of a Friend TC_25 _18 1. User should be logged in to the application. 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. 1. User sees the history of other users who allow their history to be shown by other users. 20

22 / Fail Help Menu TC_26 _19 1. The user should have logged in to the system. 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. 1. The system shows a short information about the screen. This facility is valid in all screens. / Fail 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 ( ), PowerVR SG540 Graphic Card. 21

23 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 Software Design Description System Requirements Specification Software Test Document ISBN Definition A document that completely describes all of functions of a proposed system and the constraints under which it must operate. 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) A document that detailing a systematic approach to testing a system such as a machine or software. The International Standard Book Number (ISBN) is a unique numeric commercial book identifier. 22

24 IEEE RESTful Eclipse IDE Android Tomcat Apache JMeter 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. An approach for getting information content from a Web site by reading a designed Web page that contains an ML. A multi-language software development environment A mobile device operating system developed by Google Inc. An application server from the Apache Software Foundation. A desktop application that is designed to load test functional behavior and measure performance Traceability Matrix s: Requireme nts from SRS TC_1 TC_2 TC_3 TC_4 TC_5 TC_6 TC_7 23

25 TC_8 TC_9 TC_10 TC_11 TC_12 TC_13 TC_14 TC_15 TC_16 TC_17 TC_18 TC_19 TC_20 TC_21 TC_22 TC_23 TC_24 TC_25 TC_26 24