Home

System Test Plan (Maverick Volunteer Tracking System)

1. Token Controller PDF Generator GCM Sender Android Database Remote Database 65 TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 7 1 2 7 1 3 7 1 4 Component Testing Phase Component Testing will be performed on each component after completing unit test for each modules that are combined with in that component to ensure that all components are functioning properly The Component Testing will be performed by team members and will test the following subsystems Android GUI Index Pointer Page Router Web GUI Android Controller Web Controller Remote DB Controller MVTS API MVTS OAuth PDF Generator GCM Sender Android Database Remote Database Regression Testing Phase Regression Testing will be used to test the system and uncover new bugs when changes are made in the software Regression Testing will be conducted as each stage of our delivery schedule After each modules are integrated into the component we will perform regression test to ensure that it still functions as expected Some of the testing that will be included in Regression Testing will be Runallprevious test Run new tests relating to the added feature Record test results Integration Testing Phase Integration Testing will be performed to ensure the overall system is functioning after integrating all the modules and components into the layers Integration Testing will verify the functions specified in t
2. MVTS Component Controller RDB Controller Request Processor API Processor Response Generator OAuth Controller Token Controller PDF Generator GCM Sender Android Database ESEL E daa mumler Remote Database Component Android GUI I Index Pointer Page Router Integration Presentation Web GUI ndroid Controller gt Application Web Controller Remote DB Controller MVTS API P Service MVTS OAuth PDF Generator f GCM Sender i Android Database Data Storage Remote Database System Validation MVTS Maverick Volunteer Tracking System Figure 3 1 Testing Phases 31 TimeKeepers System Test Plan Al A2 A3 4 9 15 3 1 2 Android GUI Unit Tests Volunteer Tracking System The table below describes the unit tests for the different modules in the Android GUI subsystem UI display Activity View Notification View To test if all the different views are rendered properly in the Android App To test if the Activity View successfully returns an XML data to the UI display To test if notification view successfully returns a Notification object with notification data User will touch the various buttons in the Android App User Tap Reguest UI element Test UI element data corresponding to a user action will be passed to the Activity View module UI element Test Android UI element data corresponding t
3. Testing Approach Enter the Email address for validation Ensure the system requests to establish a new password Login to the system and enter both the Email and password for validation Ensure that system allows the user to view the home page after logging in 5 2 13 Logout Description The Volunteer Tracking System shall allow volunteers to logout of the system When the user is logged out the system shall redirect to the login page Risk Medium Testing Approach Login to the system as a volunteer and logout of the system Ensure that when logged out the system is redirected back to the login page 5 2 14 Register Volunteers Description The Volunteer Tracking System shall allow Admin to register volunteers and allow access into the system Risk Medium Testing Approach Login to the system as an Admin Register a new user by entering in their Email address Login to the system as the newly registered volunteer and ensure the system is able to redirect the volunteer to the home screen after verification 5 2 15 Ease of Use Description The Volunteer Tracking System shall provide a user friendly interface The system shall also limit the number of clicks to allow a user to reach their desired page easily Risk Medium Testing Approach Login to the system as a volunteer Select a page as a starting point and another page as the destination Keep a counter to track the number of click it takes the volunteer to get from the star
4. The Web GUI will send user request and user input data to the Index Pointer which will either process the request or redirect the request Based on the user request from the Web GUI the Page Router determines if there is a URL change and injects the requested page content back into the Web GUI Volunteer Tracking System MVTS API Volunteer Volunteer MVTS O Auth MVTS O Auth Web Controller Web Controller Web GUI Web GUI Web GUI Web GUI Web GUI Table 2 7 Data Flow Definition 21 GCM Sender Android GUI Web GUI MVTS API Remote Database Controller Web GUI Client Transport Volunteer Admin Facilitator Web Controller Index Pointer Page Router TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 2 2 3 Presentation Layer The Presentation Layer consists of the Web App GUI Android App GUI This layer is responsible for gathering input from the user and displaying processed information back to the user The Web App GUI consists of all the website GUI s that will allow the user to interact with the system through their computer Similarly the Android App GUI consists of all the GUT s that will allow the user to interact with the system through their Android smart phone The layer below the presentation layer is Application Layer The Presentation Layer will pass on the raw data collected from the user as input to the Application Layer Depending on the task the Ap
5. Because these modules are the smallest components of the system it is crucial that each module is tested to ensure that they are functioning properly The larger components are built from the modules Therefore it is impossible to ensure that the larger components of the system work without first proving that the modules that make them up work 4 9 15 23 TimeKeepers System Test Plan Volunteer Tracking System 3 1 Detailed Design Diagram VLI UDI Volunteer Admin Facilitato PA mk Presentation Android Contre ller Activity Controller Notification Handler H AFD4 Eed Android DB Controller Sync Adapter aa GCM1 a 1 aa HR i GCM Receiver AS AA MI Requestor H H RARR AEEE ERA EE ER EER EE EE RR EE EE ER E ARE EER ER EE NEE EE RE EE ER wawsnaanan mawaananwananaanumannanamanananaanananan ST5 Internet itre RDB Controller AP4 Request Processor OAuth Controller OG TCI Token Controller atabase emote Database Android Database pot Remote Database B Data Storage GCM1 External Services GCMAPI Figure 2 3 Module Decomposition Diagram 4 9 15 24 TimeKeepers Volunteer Tracking System System Test Plan 2 3 2 Producer Consumer matrix IdV N99 osedeled ajouoy seqe1eq ploupuy TOON dapuas NDD JOJe13U30D 4dd TimeKeepers 48 041U0 u yo l 13 01J40 YINYO Jolej u p asuodsay JOSS3901d IdV 10SSa201d 1s nb u 43 0 114
6. User requests The correct and incorrect data for username and password will be submitted to verify that correct actions are taken in each step The user clicks on logout button to logout of the system In the admin page required credentials to register volunteers into the system are entered to verify that new user is added to the system The various number of hours volunteered are entered in the specific page After new events are created or numbers of volunteered hours is added System should send notification to relevant users The opportunities com mitment will be added edited deleted and signed up to verify that the information in the database is changed The request will be provided to generate and manage reports to 50 Volunteer Tracking System The System logs Critical the user in after successful username and password validation The system logouts user after clicking logout button System shall Critical register new volunteers The System Critical modifies updates relevant data in the database System notifies High user about relevant changes The System High modifies updates relevant data in the database The System shall High generate manage relevant reports TimeKeepers System Test Plan 4 9 15 V7 V8 v9 Verify Ease of Use Promote Members De mote Facilitators Verify Web Browser Compatibility 522 User Inspection Us
7. see the notification upon logging in to the system Risk Medium Testing Approach Login to the system as a volunteer and input the time volunteered for an opportunity Login to the system again as a facilitator and ensure that notifications are visible for the volunteered hours for that particular member Input Volunteer Hours on Behalf of User Description Upon the reguest of the volunteer facilitators must be able to input the volunteer hours on behalf of the volunteer The facilitators shall be able to see a list of all members and an option to input their volunteer hours The facilitator will have access to input the volunteer hours of all members without any time limitations or constraints Risk Medium Testing Approach Login as a facilitator into the system and select a member Ensure that the system allows an option to input volunteer hours on behalf of the volunteer Add Volunteer Opportunities Description The Volunteer Tracking System shall allow facilitators to input the new or upcoming volunteer opportunities An opportunity may include a title description date and time location and images Risk Low Testing Approach Login to the system as a facilitator and input a new volunteer opportunity Ensure that the system accepts a new opportunity by the facilitator Delete Volunteer Opportunities Description The Volunteer Tracking System shall allow facilitators to delete volunteer opportunities previously entered into t
8. Database Controller Server Transport Server Transport Server Transport Server Transport Server Transport MVTS API MVTS API MVTS API MVTS API Web GUI Server Transport MVTS O Auth MVTS API Server Transport MVTS API Remote Database Client Transport GCM API Remote Database Controller Remote Database Controller MVTS O Auth PDF Generator TimeKeepers System Test Plan VA4 VLI VL2 vol VO2 WC1 WC2 WGI WG2 WG3 WG4 WG5 4 9 15 The MVTS API notifies the GCM Sender to send an alert to the GCM API whenever an update in the Remote Database should affect the Android Database The Volunteer will input data including touch data into the Android GUI The Volunteer will input data into the Web GUI The MVTS O Auth Subsystem provides information back to the MVTS API on the state of validation The MVTS O Auth Subsystem checks user s credentials with credentials stored in the Remote Database via the Remote Database Controller The Web Controller will relay what needs to be displayed to the user in the Web GUI The Web Controller will format and send user input data to the Client Transport which will then be processed by the Service Layer The Web GUI will display information to the Volunteer The Web GUI will display information to the Admin Facilitator The Web GUI will send user request and user input data to the Web Controller for processing
9. Layer responds correctly to all the user requests The Application Layer updates Android Database after Remote Database is updated The data is retrieved or stored in the database and result is shown to the user The user verification status and session status is returned and requested actions from Application Layer are processed The Service layer provides Application Layer with JSON response pertaining to the request The Data Storage Layer stores and retrieves properly from Remote and Android Databases Volunteer Tracking System Fails to respond correctly to all user requests Fails to update Android Database Fails to retrieve data stored in the database Fails to return user verification status and session information Fails to process requested actions from the Application Layer Fails to provide the Application Layer with JSON responses corresponding to the requests Fails to store data properly in the Remote and Android Databases Fails to retrieve data properly from the Remote Database Table 8 3 Integration Testing Acceptance Criteria 8 4 System Validation Test ID System Test 4 9 15 VI V2 V3 V4 v5 Verify Login and Logout Register Volunteers Verify input volunteer hours and Track Progress Verify Notification Verify Add Edit Del ete Sign up Opportunitie s commitmen t Pass Criteria The System logs the user in after successful username and password validation The system l
10. P ee ee Re ee e 61 5 1 3 Responsive Design a a ka N NE Ee evel ee EWE N A a eden Ee ed deet Cast SW dele a ee Ge ee es ges 61 6 Features Not To Be Tested n m ese gs see Se ee i L Pe Be ee ee ee ee Ee ee Pe ke a ae ee Ee Roe Sus 2 62 SA BES GR SG ENE 65 Jl Unit Testing Pha e E aii Rd 65 71 2 Component Testing PHASE ER a Ee iz 66 7 13 Regression Testing Ph8862u u n n EES Ee tens Ee ee dann RS Ee GE asas KOS ek EN EE Reg eg ge qaqa asa u ee serial 66 TLA Integration Testing Phase rar er dusk EE Re Ee Ge teh L di banned ee ee Ee RE 66 7 1 5 System Validation Testing Phase sesse ees sede se ee ER Ee GE AA ee ee de ed E Ee AA qhapa AE Ee AE ee eg ed eie 67 Bi Acceptance Criteria td u aus 68 9 Test Delmverables mun ensen Mek Gi Met eet SEN ee eb late 74 4 9 15 3 TimeKeepers System Test Plan Volunteer Tracking System E A O Nee en aaa ee EER 76 Li APprovals aa an ER EE EE rs een 78 4 9 15 4 TimeKeepers System Test Plan Volunteer Tracking System Document Revision History Revision Number Revision Date Description Rationale 0 1 03 31 2015 Official First Draft First draft complete 1 0 04 02 2015 Review Ready Validated the consistency and the formatting of the document the Draft is ready for review 1 1 04 07 2015 Peer Review Changes Made corrections based on the feedback received from team Ground Control 2 0 04 09 2015 Baseline Version Added remaining test cases and fixed the formatting of the document 4 9 15 5
11. Traceability Matrix 4 9 15 29 TimeKeepers System Test Plan Volunteer Tracking System 3 Test Items 3 1 Unit Testing 4 9 15 3 1 1 Description The Maverick Volunteer Tracking System will be tested with 4 different phases The different phases are Unit Test phase Component Test phase Integration Test phase and System Validation test phase The Unit Test phase will test the individual modules of all the subsystems in the system This is the most detailed of the test phase Moving up the hierarchy we have Component Test phase which will test the system on the subsystem level This test will check if all the subsystems are functioning properly or not The Integration testing will test the different layers of the system The layers will be isolated with each other and tested separately to identify any faults in the layer interfaces or the layer itself Lastly we have the System Validation test which will verify if the system correctly fulfills all the system requirements The test cases in this phase will map to each of the critical requirements The diagram below shows how the testing phases are broken down 30 TimeKeepers System Test Plan Volunteer Tracking System UI Display Activity View Notification View Index Pointer Page Router Index View MVTS Page MVTS Component Activity Controller Android DB Controller GCM Receiver Notification Handler Sync Adapter MVTS API Requestor AJAX Handler
12. call should be returned TimeKeepers System Test Plan 3 1 7 Web Controller Unit Tests Volunteer Tracking System The table below describes the unit tests for the different modules in the Web Controller subsystem WC1 WC2 4 9 15 AJAX Handler MVTS Component Controller To test if AJAX Handler returns a JSON response for loading a page To test if 1t returns a formatted JSON data whenever a JSON request for a MVTS Component data is made JSON Request JSON Request A JSON request for an MVTS Component data will be made to this module A JSON request for an MVTS Component will be made to this module with a sample test script Table 3 6 Web Controller Unit Tests 37 The module should return a JSON Response containing the requested MVTS Component data The module should return a formatted JSON response containing all the necessary data to load an MVTS Component in the GUI High High TimeKeepers System Test Plan Volunteer Tracking System 3 1 8 Remote DB Controller Unit Tests The table below describes the unit tests for the different modules in the Remote DB Controller subsystem Test ID Module Test Detail Expected Result Priority Purpose Input RC1 Remote DB To test if Parsed String array String array High Controller SQL String data containing asa result queries can for creating data for set for the be SOL SOL reguested performed queri
13. it as a means to determine strategy for increasing volunteer participation 9 TimeKeepers System Test Plan Volunteer Tracking System 1 4 1 4 1 1 4 2 1 4 3 1 4 4 4 9 15 Based on our current analysis the system will have three levels of users which include admin facilitator and volunteers The facilitators will be able to add new events to Inform the volunteers and the volunteers will be able to log their time signup for an event and view their progress The admin will be able to manage all the users as well as make changes to the system content The Volunteer Tracking System can be easily accessed under the uta edu engineering webpage or through any phone with android version 4 1 2 or above The app will be available to download from the Google Play Store Once the app is downloaded onto the phone the user will start it for the first time This will require them to enter their Email and password used to create the account Once they have been validated the internal database syncs and receives the data from the external database to display the necessary information to the user Test Scope The System Test Plan is necessary to ensure product design and implementation meets the product as specified in the System Requirements Specification and the Detail Design Specification It will be used to validate and verify the status of the prototype and its components with respect to whether it is working as expected it doesn t wor
14. properly performed respective from the with queries remote database should be database test scripts returned Table 3 13 Remote Database Unit Tests 3 2 Component Testing 3 2 1 Description Component Testing will be performed on each component to ensure that all components are functioning properly after completing unit test for each module The Component Testing will be performed at subsystem levels of the system The subsystems will be supplied with test data and compared to the expected outcome to ensure that modules with in the subsystem are functioning together properly and as expected 4 9 15 41 TimeKeepers System Test Plan 3 2 2 Presentation Layer Component Test Volunteer Tracking System The table below describes the component tests for the different subsystems in the Presentation Layer AGI AG2 IP1 PRI WGI 4 9 15 Android GUI Android GUI Index Pointer Page Router Web GUI To test if Android GUI can display different views and visual changes with the user tap to display to the user To test if Android GUI is successfully relaying user input data to the Android Controller To test if the index pointer returns the correct Full path URL upon receiving a subdirectory URL request To test if the page router returns the relevant HTML content to the index view To test if Web GUI retrieves the user interaction through various buttons and forms and display results
15. system to the customers Rationale This maintenance requirement Is not testable Other metrics such as unit component Integration and system verification testing will used instead to ensure the system Is performing and functioning as expected 64 TimeKeepers System Test Plan Volunteer Tracking System 7 Overall Test Strategy 7 1 Testing Phases 4 9 15 This section will cover the overall strategy for testing Maverick Volunteer Tracking System to ensure that it meets the requirements defined in System Requirement Specification and to verify that the construction of the product is consistent with the architecture defined in the Architecture Design Specification and Detail Design Specification 7 1 1 Unit Testing Phase The Unit Testing will be performed in each unit and module to test the function and prevent any system errors and malfunction before integrating all the modules to component Unit testing phase will be performed by each developer developing specific module and will cover the following modules UI Display Activity View Notification View Index Pointer Page Router Index View MVTS Page MVTS Component Activity Controller Android DB Controller GCM Receiver e Notification Handler Sync Adapter MVTS API Requestor Ajax Handler MVTS Component Controller RDB Controller Request Processor API Processor Response Generator OAuth Controller
16. table below describes the unit tests for the different modules in the PDF Generator subsystem PD1 4 9 15 PDF Generator To test if a PDF document is generated in the Server upon receiving user request Raw String data containing all the information for the requested report Test report data necessary for creating a report will be passed as a string to the PDF Generator module as a function call Table 3 11 PDF Generator Unit Tests 40 URL for the Medium generated PDF report document should be returned Upon entering the URL in a web browser the PDF document should be opened TimeKeepers System Test Plan Volunteer Tracking System 3 1 13 Android Database Unit Tests The table below describes the unit tests for the different modules in the Android Database subsystem AD1 Android To test 1f SQL lite Various SQL lite High Database data can be database SQL lite result sets as stored and query queries will String array retrieved be corresponding properly performed to the queries from the with test should be android scripts returned database Table 3 12 Android Database Unit Tests 3 1 14 Remote Database Unit Tests The table below describes the unit tests for the different modules in the Remote Database subsystem RD1 Remote To test 1f MYSQL Various Result sets as High Database data can be database MySQL String array stored and query queries will corresponding retrieved be to the
17. testing strategy presented in the document 2 1 System Requirement Specification This section lists the requirements listed in the System Requirement Specification It outlines all the requirements that have been determined by the members of TimeKeepers and the project sponsor Dr Linda McCalla The requirements that will be consider for testing purpose are customer requirements packaging requirements performance requirements safety requirements and support and maintenance requirements All these requirements are listed below 2 1 1 Customer Requirements 3 1 Input Volunteer The Volunteer Tracking System shall allow a Critical Hours user to input the hours volunteered To input the hours the volunteers shall be able to select the name of the opportunity from a dropdown associated with a category and enter the number of hours they volunteered along with comments 3 2 Notify Admin The Volunteer Tracking System shall also notify High the admin and the opportunity category facilitator when members input their time volunteered 3 3 Input Hours on Upon the request of the volunteer facilitators Critical Behalf of must be able to input the volunteer hours on Volunteers behalf of the volunteer The facilitators shall be able to see a list of all members and an option to input their volunteer hours The facilitator will have access to input the volunteer hours of all members without any time limitations or constraints 3 4 Add Volunteer Th
18. the Web GUI The Android GUI will display information to the Volunteer The Android GUI will relay user input data to the Android Controller The Client Transport will send data to the Android Controller from the Service Layer The Client Transport will send data to the Web Controller from the Service Layer The Client Transport will send data from either the Android Controller or Web Controller to the Server Transport The GCM API will send an alert to the Android Controller notifying it of a change In the Remote Database The GCM Sender sends an alert to the GCM API via the Server Transport notifying it of a change in the Remote Database Depending on the user input data user request received from the Web GUI the Index Pointer will redirect the user request or process the request 19 Volunteer Tracking System Android Controller Android Controller Android Controller Android Database Admin Facilitator Android GUI Android GUI Client Transport Client Transport Client Transport GCM API GCM Sender Index Pointer Android GUI Client Transport Android Database Android Controller Web GUI Volunteer Android Controller Android Controller Web Controller Server Transport Android Controller Server Transport Web GUI TimeKeepers System Test Plan PGI PRI RD1 RDC1 RDC2 RDC3 ST1 ST2 ST3 ST5 ST6 VAI VA2 VA3 4 9 15 The PDF Generator sends th
19. 0 31 13 Android Database Unit Tests id dioss 41 3 1 14 Remote Database Unit TES ica res AA Se bes ooh A aa a dde 41 A DAT ER IE EA RD Me ee ie 41 4 9 15 2 TimeKeepers System Test Plan Volunteer Tracking System 3 2 2 Presentation Layer Component Test u a Suma s aaa aa use ee 42 3 2 3 Application Layer Component Test ee ee Re ee GR Re RA ee ee ee ee ee Re ee ee 43 3 2 4 Service Layer Component Test EE EER EES GES a deer AD Ee Ceat ere ansieae ade Ee Ge ee Gee ee 45 3 2 5 Data Storage Layer Component Test a aaa nasa nas ah ush an ss A s sss 46 Eer I DIET onI o t WE AE AE E E AE A EE oe ie 47 3 32 Integration Testa ni e A E O E E TE PE 47 34 MID ESCEIP UO Mig EEn 49 3 42 System Validation Test seen oe EE jan Ard 49 A RISKS ER EE ER EE AE EE ER EE EE kne 52 5 Features To Be Tested a A s RA Ee Re ie awa ee Ve deena dent arne 53 5 2 1 Input Volunteer HOUTS S sere Re ss EG oe SEGE SEE Ge Sek cia 53 522 Not Admins 54 5 2 3 Input Volunteer Hours on Behalf of User an RA ee ee ee ee ee Re ee ee 54 5 2 4 Add Volunteer Opportunities a s s 54 5 2 5 Delete Volunteer Opportunities SS RES Suman ER E A E eg ee uay i 54 5 2 6 Sign Up for Volunteer Opportunities u u n nunn niea as qani ee Re ee a auqa aa 55 5 2 1 Caneel Commitment seh uu y pa EO REGIE GE EES GER Ee AA Dee SEA Glesser 55 5
20. 09 OU J AI 3SU811 JANIS J13A199SUB 1U3ID lt aX lt 19 01JUO 1U3UOdWO SLAN 4 pueH XVIV 4o1sanbay Id V SLAN N daydepy 2uAs AC 2 o o gt lt J9M399Y NID 25 49 1013409 qq PlOJPUY Ja pueH UONEIYNON gt 48 041U0 AWAY lt u Ar 1U3UOdWO SLAN a8ed SLAN Ja noy 934 MAA X pul 181uI0d x pul a OE MIA UONENON m id N IA HANDV a N Aejdsip In 10 811 1984 UWpy gt J99IJUNJOA ri ri gt N volunteer Admin Facilitator JI display Activity View Notification View ndex Pointer ndex View age Router MVTS Page MVTS omponent Activity ontroller A zi Notification dandler Android DB ontroller oy 3CM Receiver sync Adapter MVTS API requestor 4 9 15 ATA Y Handlar System Test Plan Volunteer Tracking System MVTS Jomponent Jontroller Fa gy Cy SE Jlient ransceiver 4 A N AOMOOS CT server ransceiver ST Ao Ao Ao Ao RDB Controller RC Request Processor me PH VD Z ra ry gt API Processor response 3enerator Po 2 Auth Controller O O O Token Controller ad DF Generator ROA 3CM Sender Za Android Database o emote Database o
21. 218 Notify Ee Te EE ar RR RE EE EE qasa qaqa Tacita 55 5 2 9 Track Proores suna na RN RR 56 5 2 10 Generate Reports ES A Ad 56 S 2 11 Customize Preferences si u ea cias 56 MA EER EE EE RN 56 Di DDO BOUL SR ER EE Sa m m Su EE EG EG EE EE ED u EG EE OG Ge De u ED 57 5 2 14 Register Volunteers is Ee EE SEGE te aid 57 5 2 15 Ease of Use EE EE EE EE N RE ER N N aa 57 5 2 216 ANdroid Applicat OM vic ER un n uu uuu DE AR DEE eg base Ge ie ee N ee EG ER SE Ge RR De 57 Sid Website ME IE EE EE RE EE qaa OE 58 2 32 Page URS uum SS li A east 58 5 3 3 Installation SEFIPE SG RS PER GE Ac 58 S Application Response Time EE dd 59 54 2 Dynamic Page Update ss Ee ee eed eN EE ee se da eden der ke dek aW a ee pt deed 59 4 3 File COMPE NA au E Su isan See ee ee au De Ee inn ie ee Guau oe Ee De Ee EE u 012 59 5 5 1 Password Encryption T uy u utu ee ee ansa GR Re ee GRA GRA um aS GR de RA ee ee au t qz 59 5 5 2 Malicious Input Protection a ES BE Re decker EN Ee sg Ee SE n Pe Gee S See Ee Ee ER dennen Be Ee se ge ek Ee Ee Gee EER 60 5 6 WA ed m l Version Support ER EE ee Suha EG OD ER eN Ds Ee ee ee EG OG Ee GE ee GO ER GE Ge api 60 5 62 Android Version SUpporti 1 es terts r i awia ee deer RES Ee GE asas KOS ek eeen eggs bed ove den rs See DE bee 60 3 63 User Manual u se EE iene bee tel aed duk EE E RE Nd beech a ete 60 5 7 1 Web Browser Compatibility canica haapa aen eg atea 61 5 7 2 Web Service Code Compatibility sesse u un au au q u a a ee ee RA
22. 4 2 6 4918 443 10 Test Schedule Testing Phase Phase 1 Unit Testing UI display Activity View Notification view Index pointer Index view MVTS page MVTS component Activity controller Android DB controller GCM Receiver Notification Handler Sync Adapter MVTS API requestor AJAX Handler MVTS Component Controller RDB Controller Request Processor API Processor Response Generator OAuth Controller PDF Generator Token Controller GCM Sender Android Database Remote Database Page Router Phase 2 Component Testing Android GUI Web GUI Android Controller Web Controller MVTS API MVTS OAuth Phase 3 System Verifigation and validation Volunteer Tracking System 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 19 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 30 15 5 07 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 25 15 4 30 15 4 30 15 4 30 15 4 30 15 4 30 15 4 30 15 4 30 15 5 05 HmeKeepers System Test Plan Volunteer Tracking System testing 3 4 4 3 1 1 Presentation Layer Testing 4 30 15 5 05 1
23. 5 3 4 4 3 1 2 Application Layer Testing 4 30 15 5 05 15 3 4 4 3 1 3 Service Layer Testing 4 30 15 5 05 15 3 4 4 3 1 4 Data Storage Layer Testing 4 30 15 5 05 15 3 4 4 3 2 Validation 5 05 15 5 07 15 Table 10 1 Test Schedule 4 9 15 77 TimeKeepers System Test Plan Volunteer Tracking System 11 Approvals Mr O dell Project Supervisor sr Dr Linda McCalla Project Sponsor Dineth Hettiarachchi Team Leader O Devkishen Sisodia Team Member Tasneem Devani Team Member f Damber Khadka Team Member Samir Shrestha Team Member IR Table 11 1 Approval ignatures 4 9 15 78 TimeKeepers
24. 9 15 Risk Web Server connection fails Database access fails Inaccurate Data GCM Server connection fails Adding new requirements towards the end of the project Impact User will not be able to connect to the website and the Android App will not be able to connect to the website MVTS is unable to connect to the database to retrieve or send information Incorrect data being sent to the database can result in inaccurate data being represented Android App may not be able to accurately send notifications to the device Can result in new bugs in the system Table 4 2 Risks 52 Severity High High Medium Medium Medium Mitigation Strategy Ensure UTA s server is live and functioning Ensure that database connection is properly set up and each request is authorized Ensure the data being passed is accurate by allowing the admin to verify the input Verify if the App is able to properly connect to the GCM server to send notifications to the device Test all affected functions and continue the component and integration testing after each change TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 5 Features To Be Tested This section covers the features to be tested Features are associated with a risk level that is described below along with the testing approach The risk levels are described below 5 1 Risk Definitions 5 1 1 High This feature s implemen
25. Department of Computer Science and Engineering The University of Texas at Arlington tumeKeepers Team TimeKeepers Project Volunteer Tracking System Team Members Dineth Hettiarachchi Damber Khadka Devkishen Sisodia Samir Shrestha Tasneem Devani System Test Plan Volunteer Tracking System Table of Contents DOGuinient Revision History a5 6 n tinnen ici 5 LAO EIE ES astaq o at a o o h edo hears de 6 EROS EE ER A en er bq delenit oa ss asa 7 esa Introduction ME NNN 9 1 1 Lest Plan OVERVIEW s l a AA cables SA a u SS er desea he G aa H kaier 9 12 Product Gie EE EE aa RE N ada cose aha aaa dla stede 9 1 35 Product RO 9 EIS O NN 10 O NO O 12 2 1 System Requirement SpecifiCaHOR is Ge ie Ge Re EE Ge ade Ee ee Se De oe Ee a da beeen e S 12 21 1 Customer Requirements sd se A Sua qusa yas ee ee ee A Ee asua 12 2 12 Packaging Requirement russen anan e Sek anu EER E A Se Koo REED ke Ee eek oe hete oware 14 2 1 3 Performance Requirements ME GE ES SN 15 2 1 4 Security and Privacy Requirement esse esse ees se ee ee a u u u a a a Qu ee ee ee ee Re ee ee 15 2 1 5 Maintenance and Support Requirements Re RA RA AA ee ee GR Re RA ee ee ee ee Re ee ee 16 2 1 6 Others Requirements u un u S n up SS S a u u aun Ina S PSS Sunqu s 17 2 2 Architecture Design Specification au u u qu Nee i a ua aaa u anna SEE Ge ee Ne eie 17 22 1 Architecture Design Diagram moerassen Ol Gegee ed a
26. Do JCM API P2900 4 9 15 Table 2 8 Producer Consumer Matrix 26 TimeKeepers System Test Plan Volunteer Tracking System 2 3 3 Requirement Traceability Matrix 2 3 3 1 Presentation Layer Req No ES Module Name UI Activity Notification Index Page Index MVTS MVTS display View View Pointer Router View Page Component 3 1 Input X X X X Volunteer Hours 32 Notify Admin x x 3 3 Input X X X X Volunteer Hours on behalf of user 3 4 Add X X X X Volunteer Opportunities 3 5 Delete X X X Volunteer Opportunities 3 6 Sign Up for X X X X X Volunteer Opportunities 3 7 Cancel X X X Commitment 3 8 Notify X X Volunteer 3 9 Track X X X X Progress 3 10 Generate X X X X X Reports 3 14 Customize X Preferences 3 15 Login X X X X 3 16 Logout X X X 3 18 Register X X X Volunteers 3 23 Android X X X Application Table 2 9 Presentation Layer Modules Traceability Matrix 4 9 15 27 TimeKeepers System Test Plan 4 9 15 Req No 3 1 3 2 3 3 3 4 3 5 3 6 3 7 3 8 3 9 3 10 3 14 3 15 3 16 3 18 3 23 2 3 3 2 Application Layer Requirement Name Android DB Controller Activity Controller Input Volunteer Hours Notify Admin Input Volunteer Hours on behalf of user Add Volunteer Opportunities Delete Volunteer Opportunities Sign Up for Volunteer Opportunities Cancel Com
27. Request a member from another team to use this installation script on their local server to ensure the necessary database tables are properly populated 58 TimeKeepers System Test Plan 4 9 15 Volunteer Tracking System 5 4 Performance Requirements 5 4 1 5 4 2 5 4 3 Application Response Time Description Response time between user interaction and result should be less than 8 seconds in both the website and the Android app Risk Medium Testing Approach Login to the system as a volunteer and test any Input a user may make in the application to ensure the response time is less than 8 seconds Dynamic Page Update Description Only the necessary parts of the web page will be updated upon the user Interaction instead reloading the page completely Risk Medium Testing Approach Login to the system as a facilitator and enter a new opportunity into the opportunities page Ensure that only the opportunities are refreshed and not the entire page File Compression Description JavaScript and CSS files will be compressed to reduce the file size Size of JPEG images should be less than 3 MB Risk Medium Testing Approach When uploading the files to the server compress the JavaScript and CSS files Check the compression size and of the files and ensure that it is not more than 3 MB 5 5 Security and Privacy Requirements 5 5 1 Password Encryption Description All the user passwords shall be encrypted in the MySQL
28. TP response message containing the user action requested data should be generated by this module High High The table below describes the unit tests for the different modules in the MVTS OAuth subsystem MO1 OAuth To test if User Username and Boolean High Controller OAuth validation password string variable Controller request will be send to indicating returns a this module authenticati Boolean upon on status receiving user will be name and returned password MO2 Token To test ifa Token User login MO2 Token Controller token is update session Controller generated request information such upon user as username and authentication password will be by OAuth send to this Controller module Table 3 9 MVTS OAuth Unit Tests 4 9 15 39 TimeKeepers System Test Plan 3 1 11 GCM sender Unit Tests Volunteer Tracking System The table below describes the unit tests for the different modules in the GCM sender subsystem G1 GCM Sender To test if GCM sender sends a String data containing remote database update information to the GCM Server Raw String data containing information about the database insert update request This module JSON High will be Object invoked containing with an information insert update about request to updated the remote rows in the database in Remote DB order to should be trigger the generated GCM Servers Table 3 10 GCM Sender Unit Tests 3 1 12 PDF Generator Unit Tests The
29. TimeKeepers System Test Plan Volunteer Tracking System List of Figures FIGURE TITLE PAGE 1 1 High Level System Diagram 11 2 12 Architectural Diagram 18 2 3 Detailed Design Architecture Diagram 24 3 1 Testing Phases 31 4 9 15 6 TimeKeepers System Test Plan Volunteer Tracking System List of Tables FIGURE TITLE PAGE 2 1 Customer Requirements 12 2 2 Packaging Requirements 14 2 3 Performance Requirements 15 2 4 Security and Privacy Requirements 15 2 5 Maintenance and Support Requirements 16 2 6 Other Requirements 17 DA Data Flow Definition 19 2 8 Producer Consumer Relationship 25 2 9 Presentation Layer Modules Traceability Matrix 27 2 10 Application Layer Modules Traceability Matrix 28 2 11 Service and Data Storage Layer Modules Traceability Matrix 29 3 1 Android GUI Unit Tests 32 3 2 Index Pointer Unit Tests 33 3 3 Page Router Unit Tests 33 3 4 Web GUI Unit Tests 34 3 5 Android Controller Unit Tests 35 3 6 Web Controller Unit Tests 37 3 7 Remote Database Controller Unit Tests 38 3 8 MVTS API Unit Tests 38 3 9 MVTS OAuth Unit Tests 39 3 10 GCM Sender Unit Tests 40 3 11 PDF Generator Unit Tests 41 3 12 Android Database Unit Tests 41 3 13 Remote Database Unit Tests 42 3 14 Presentation Layer Component Tests 43 4 9 15 7 TimeKeepers System Test Plan 3 15 3 16 3 17 3 18 3 19 4 2 7 3 8 1 8 2 8 3 8 4 10 1 11 1 4 9 15 Application Layer Component Tests Service Layer Component Tests Data Storage Layer C
30. User Tap Request User Input Subdirectory URL requests URL request User input click action 42 Various views in the app will be tapped to check if all the pages are displayed correctly Methods will be called to send the user inputs information and check if it is sending data correctly Index Pointer will be called with a subdirectory URL request for one of the pages in MVTS pages The page router will be invoked with a URL request for a HTML page Various pages will be clicked and various inputs will be entered to check if all the pages and The Android GUI should display different Views corresponding to the user actions The Android GUI should relay user input data to Android Controller Index pointer should point all the subdirectory URL requests to the base directory path The Page Router should return HTML content corresponding to the URL request The Web GUI should display different vlews and results corresponding to the user actions TimeKeepers High High High High High System Test Plan WG2 Web GUI WG3 Web GUI to the user To test if Web GUI retrieves the user Interaction through various buttons and forms and pass it to Web Controller To test if Web GUI retrieves all the MVTS component needed for each specific page in the form of HTML content Table 3 14 Presentation Layer Component Tests User input click a
31. abase upon receiving notification about changes in Remote Database To test if Android Controller successfully pushes API calls via HTTP Request to send and receive data from the MVTS API subsystem To test if Web Controller is relaying results pertaining to user request back to the user To test if Web Controller successfully responds to all the events generated by user through Web GUI and relay it to the Parsed String data GCM API response data and JSON object containing synchroniz ation data JSON Object JSON Response HTTP Request 44 Sample string of array containing SQLite query will be send to check if Android Controller is retrieving information correctly from Android database Sample SQLite queries for updating the database will be sent to Android Database to update Android Database A Synchronization request will be made to MVTS API to check if API calls are successfully pushed A set of JSON response will be provided to see if Web Controller is converting to HTML and passing results back to the Web GUI A HTTP request pertaining to the events generated by user will be sent to check if correct HTTP request is made to MVTS API Volunteer Tracking System create an activity view The Android Controller receives result set from Android Database depending on the request High The Android Controller should update Android Database upon recei
32. credentials will be checked with remote String array as a result set for the requested SQL query should be returned back High The MVTS API should respond to the various API calls pertaining to the request and provide the requested data High The MVTS High OAuth should receive either TimeKeepers System Test Plan PG1 GS1 PDF Generator GCM Sender To test ifa PDF document is generated in the Server upon recelving user request To test if GCM sender sends a notification regarding update on the remote database to the GCM Server Raw String data Notification Response database to validate user A request will be made to generate PDF through test script This GCM Sender will be invoked with an update in the remote database in order to trigger the GCM Servers Table 3 16 Service Layer Component Tests 3 2 5 Data Storage Layer Component Test Volunteer Tracking System successful user validation or unmatched user credentials URL for the generated PDF report document should be returned The GCM High Senders should notify GCM Server about changes in remote database Medium The table below describes the component tests for the different subsystems in the Data Storage Layer AD1 Android Database 4 9 15 To test if data can be stored and retrieved properly from the android database SQLite Various SQLite result High da
33. ction HTML import request 3 2 3 Application Layer Component Test results are displayed correctly Methods will be called to send the user request and check if it is making successful reguest HTML import request for a MVTS Component will be send through a test script to check 1f correct MVTS component is returned Volunteer Tracking System The Web GUI should relay user input data to Web Controller High The Web GUI should receive all the MVTS components in the form of HTML content needed for each specific page High The table below describes the component tests for the different subsystems in the Application Layer ACI Android Controller 4 9 15 To test if the Android Controller retrieves the Activity Object containing all the details for constructing an Activity View User Input data 43 A sample user input data request such a user pressing a profile button will be used to invoke the Activity Controller The Android Controller should receive and return an object to containing all the necessary information to High TimeKeepers System Test Plan AC2 Android Controller AC3 Android Controller AC4 Android Controller WC1 Web Controller WC2 Web Controller 4 9 15 To test if Android controller can successfully request and receive the result set data from the Android Database To test if Android Controller can successfully update Android Dat
34. d High HTML content data for the requested MVTS Component should be returned back as a HTML String data High TimeKeepers System Test Plan 3 1 6 Android Controller Unit Tests Volunteer Tracking System The table below describes the unit tests for the different modules in the Android Controller subsystem ACI Activity Controller AC2 Android DB Controller AC3 GCM Receiver 4 9 15 To test if the Activity Controller returns the Activity Object containing all the details for constructin gan Activity View To test if the controller receives the result set data from the Android Database To test if the GCM receiver notifies the SYNC adapter when GCM receiver receives database update notification from GCM Sender User Input data A sample user Parsed String data GCM API response data 35 input data request such a user pressing a profile button will be used to invoke the Activity Controller module String array containing query string will be send to the module GCM API response data containing the information about update made to the remote database will be used to invoke the GCM receiver module The module should return an object containing all the necessary information to create an activity view which can be rendered by the UI display module The module should return a String array containing data for the requested query The module should
35. database Risk Low Testing Approach Access the database and request the password of the accounts created Ensure that passwords are encrypted when returned 59 TimeKeepers System Test Plan 4 9 15 5 5 2 Volunteer Tracking System Malicious Input Protection Description System shall validate all the input data to ensure that the entered data is correct and or user has not entered any malicious code in any input fields Risk Medium Testing Approach Insert incorrect data and ensure that the system is able to detect and respond with an appropriate notification to the user 5 6 Maintenance and Support Requirements 5 6 1 5 6 2 5 6 3 PHP Version Support Description The UTA servers are running PHP version 5 1 Therefore the web application shall be compatible with PHP version 5 1 Risk Medium Testing Approach Run the application on PHP version 5 1 on the local server and ensure that the application works as expected without any issues Android Version Support Description The mobile version of the system will be Android based The application will support a minimum API level of 16 which corresponds to version 4 1 2 Jelly Bean Risk Medium Testing Approach The system will be tested on a different Android device running version 4 1 2 and above The team will ensure that MVTS runs on this device without any issues User Manual Description The team will provide user manual that describes the different
36. e Volunteer Tracking System shall allow High Opportunities facilitators to input the new or upcoming volunteer opportunities An opportunity may include a title description date and time location and images 4 9 15 12 TimeKeepers System Test Plan 4 9 15 3 5 Delete Volunteer Opportunities 3 6 Sign Up for Volunteer Opportunities 3 7 Cancel Commitment 3 8 Notify Volunteer 3 9 Track Progresses 3 10 Generate Reports 3 11 Manage Reports 3 12 Promote Members Volunteer Tracking System The Volunteer Tracking System shall allow facilitators to delete volunteer opportunities previously entered into the System If volunteers have committed to an opportunity and it is cancelled the system will notify all volunteers through Email The volunteers shall be able to see the details of an opportunity such as the date time and location and have an option to sign up for an opportunity to indicate they will be volunteering at that opportunity The volunteers shall be able to cancel a commitment they previously made If volunteers previously signed up for an opportunity the system shall allow them to cancel their commitment to indicate they will no longer be volunteering at that opportunity The Volunteer Tracking System shall notify the volunteer and the opportunity facilitator upon the volunteer s acceptance commitment or cancellation of an opportunity This notification will be system generated The volunteer and
37. e or modify the relevant data in the database related to promoting and demoting facilitators System does not function properly in browsers such as Chrome Firefox IE 10 and Safari 6 Android App cannot be downloaded and or installed in Android devices running Android version 4 1 2 Table 8 4 System Validation Acceptance Criteria 73 TimeKeepers System Test Plan Volunteer Tracking System 9 Test Deliverables The sections below describe the test deliverable that will be made available to the stakeholders A list of bug reports will also be maintained for tracking errors in the future 9 1 System Test Plan The System Test Plan includes our overall strategy in detail for testing the system It describes our approach for testing the system in parts and a whole in different phases 9 2 Test Cases The following information will be available for each of the test cases Test ID The Unique ID for the particular test Test item The module subsystem name that will be tested Purpose The reason for conducting this test Input The Input that the test item will receive either through a test script or manually Test Description a brief description on how the test will be conducted Expected Results The expected behavior of the module upon receiving the input Priority Test priority of low medium or high 9 3 Test Report The following report will be provided for each of the test t
38. e report in PDF format to the MVTS API The Page Router will return the relevant HTML content to the Web GUI The Remote Database Controller will read data from the Remote Database via the Server Transport The Remote Database Controller will send formatted data to the MVTS O Auth for user authentication The Remote Database Controller will send formatted data to the MVTS API for further processing Data read from and inputted into the Remote Database by the Remote Database Controller will travel via the Server Transport The MVTS API receives user request data from the Server Transport Data sent to the Remote Database from the Service Layer will travel via the Server Transport The Application Layer and Service Layer will send and receive data to and from each other via the Server and Client Transports The Server Transport sends the alert created by the GCM Sender to the GCM API see GCMS1 Data sent to the Remote Database Controller from the Remote Database will travel via the Server Transport The MVTS API sends data or requests to read data to and from the Remote Database Controller MVTS API sends data or requests to read data to and from the Remote Database Controller The MVTS API sends the necessary data to the PDF Generator in order to generate a report 20 Volunteer Tracking System PDF Generator Page Router Remote Database Remote Database Controller Remote Database Controller Remote
39. e that the system indicates the volunteer is no longer attending this event Notify Volunteer Description The Volunteer Tracking System shall notify the volunteer and the opportunity facilitator upon the volunteer s acceptance commitment or cancellation of an opportunity This notification will be system generated The volunteer and the facilitator will be able to see this notification on their home page Risk Medium Testing Approach Login to the system as a volunteer and commit to an opportunity Ensure that a notification of acceptance is seen Cancel the commitment to the same opportunity Ensure that a notification of cancellation is seen Login to the system as a facilitator and ensure that both notifications are seen 55 TimeKeepers System Test Plan Volunteer Tracking System 5 2 9 Track Progress Description The Volunteer Tracking System shall allow users to track progress of their volunteer activities and the status of different service levels Service levels are different levels that volunteers can achieve based on the total number of hours The levels are divided as follows 30 60 90 150 and 150 Risk Medium Testing Approach Login to the system as a volunteer and input the listed hours for an opportunity to track the changes in the volunteer levels 5 2 10 Generate Reports Description The Volunteer Tracking System shall generate progress reports for each volunteer upon their request The progress report sho
40. ed JSON Object containing information about updated rows in the Remote DB is generated SQL lite result sets as String array corresponding to the queries should be returned Result sets as String array corresponding to the respective queries should be returned Volunteer Tracking System Fails to receive a JSON object with result pertaining to the API call Fails to format the result appropriately Fails to send the result back to the Web GUI Fails to send a JSON request pertaining to the events generated by the user Fails to receive a JSON response Fails to return a result set for the requested SQL query Fails to respond to the API calls Fails to provide requested data Fails to receive successful user validation or unmatched user credentials Fails to generate URL for the PDF URL is incorrect Fails to generate the JSON object that contains information about updated rows Fails to return result sets as String array Fails to return result set as String array Table 8 2 Component Testing Acceptance Criteria 8 3 Integration Testing Test ID H 4 9 15 System Presentation Layer Pass Criteria The Presentation Layer responds correctly to all the user requests 71 Fail Criteria Fails to respond correctly to all user requests TimeKeepers System Test Plan D Presentation Layer Application 13 Layer Application 14 Layer 15 Service 16 Service I7 Data Storage The Presentation
41. equests will be send to the Service Layer to check if it is responding correctly with relevant JSON response The request for updating Android Database with sample SQLite queries will be sent after getting notification about updates in Remote Database User s credential is checked from database to verify user Various API calls will be made to check if Service layer is responding Volunteer Tracking System The data is retrieved or stored in the database and result is shown to the user High Relevant JSON response should be returned to correspondi ng JSON request High The Application Layer should update Android Database after Remote Database is updated The user verification status and session status is returned High High The Service layer should provide Application High TimeKeepers System Test Plan I8 Service Layer I9 Data Storage 3 4 requests made by Application Layer To test if the Service layer Is inserting updat ing deleting data in remote database MySQL queries To test if data can be stored and retrieved properly from the remote database and Android Database SOLite gueries MySQL queries to the request from the Application Layer Various sample queries for insertion deletion u pdate will be sent to check if database is updated corresponding to the relevant request Various SQLite and MySQL queries will be perf
42. er Request None verify that relevant report is generated The user will try to visit all pages to ensure that they can reach anywhere on the webpage with maximum of 3 clicks In the admin page the members are promoted or demoted to verify that information is modified in the database The website will be opened in various browsers to ensure that it can be opened Table 3 19 System Validation Tests 51 Volunteer Tracking System The system allows user to reach anywhere on the website with maximum of 3 clicks High The System Moderate modifies updates relevant data in the database The System is Moderate opened in various browsers namely Google Chrome latest Internet Explorer Google Chrome and Safari TimeKeepers System Test Plan 4 1 Overview 4 Risks Volunteer Tracking System The following section contains a list of risks that may be encountered during the testing phase of MVTS This section will also cover the strategies to mitigate these risks 4 22 Risk Table The table below identifies the potential risks that the team may come across while testing the Maverick Volunteer Tracking system Each risk is associated with a risk ID risk description risk impact severity and a mitigation strategy for handling or avoiding the risk Each risk is ranked on a severity of low unlikely to occur medium likely to occur or high expected to occur Risk ID R1 R4 R5 4
43. es queries will SQL query to the be send to should be Remote the various returned database database back access methods within this module Table 3 7 Remote DB Controller Unit Tests 3 1 9 MVTS API Unit Tests The table below describes the unit tests for the different modules in the MVTS API subsystem Test Module Purpose Input Test Detail Expected Priority ID Result M1 Request To test if the Unauthenticated API call with Validated High Processor request processor API Call user login API call sends a token Request information request will validation request will be made be received to the OAuth to the back from Controller Reguest OAuth Processor controller module via module PHP unit test script 4 9 15 38 TimeKeepers System Test Plan M2 API Processor M3 Response Generator To test if API Processor generates a string array containing data for the respective API call To test if a correct HTTP response is generated for an API call Authorized API call request Raw String data containing user requested information Validated API call request will be send to the API Processor module via PAP unit test script String Array containing user action specific data will be send to this module Table 3 8 MVTS API Unit Tests 3 1 10 MVTS OAuth Unit Tests Volunteer Tracking System A string array containing all the relevant data for that particular API request should be returned by this module HT
44. functionality of product and instructions on how to use product This user manual shall support system administrator for any problems in future Risk Medium Testing Approach Review the manual thoroughly to ensure that it specifies the details on system Installation system functionalities and system specifications 60 TimeKeepers System Test Plan Volunteer Tracking System 5 7 Other Requirements 5 7 1 Web Browser Compatibility Description The web interface shall be accessible via various popular browsers such as Safari Google Chrome Mozilla Firefox and Internet Explorer Risk Medium Testing Approach The system will be tested on Safari Chrome Firefox and IE to ensure all the functionality is intact and performing as expected 5 7 2 Web Service Code Compatibility Description All The source code of the web functionality shall be compatible and portable with various platforms such as Windows Mac and Linux Risk Low Testing Approach The system will be tested on Windows Mac and Linux to ensure all the functionality is intact and performing as expected on the different platforms 5 7 3 Responsive Design Description The website shall reflow its layout to fit in for the screen resolution or the window size Risk Low Testing Approach The system will be tested on an Android device to ensure the layout fits in the fit resolution For the web browsers the team will resize the windows to various lengths and widths to e
45. hat is conducted Test ID The Unique ID for the particular test Tester The name of the member who performed the test o Date Time Stamp The date and time for the test performed o Outcome Test status of Passed or Failed o Comments comments concerning any issues with the testing process 9 4 Bug Report Based on the GitHub issues page a bug report will be provided along with the documentation that will include the following details Bug ID The unique bug Identifier Date Timestamp The date and time when the bug was found 4 9 15 74 TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 Priority Bug priority to be fixed low medium or high Tester Team member who performed the test Fixer Team member who fixed the bug if applicable Bug Description Brief description of the bug Status Current status of the bug fix effort Not Started In Progress or Completed Resolution Date Timestamp The date and time the bug was fixed if applicable 75 TimeKeepers System Test Plan 3 4 4 3 4 4 1 3 4 4 1 1 3 4 4 1 2 3 4 4 1 3 3 4 4 1 4 3 4 4 1 5 3 4 4 1 6 3 4 4 1 7 3 4 4 1 8 3 4 4 1 9 3 4 4 1 10 3 4 4 1 11 3 4 4 1 12 3 4 4 1 13 3 4 4 1 14 3 4 4 1 15 3 4 4 1 16 3 4 4 1 17 3 4 4 1 18 3 4 4 1 19 3 4 4 1 20 3 4 4 1 21 3 4 4 1 22 3 4 4 1 23 3 4 4 1 24 3 4 4 1 25 3 4 4 1 26 3 4 4 2 3 4 4 2 1 3 4 4 2 2 3 4 4 2 3 3 4 4 2 4 3 4 4 2 5 3 4
46. he user specific action Combined HTML content containing all the requested MVTS Component is generated HTML content data for the requested MVTS Component returns back as a HTML String data The module returns an object containing all the necessary information to create an activity view which is rendered by the UI display module 68 The different views are not rendered or not properly rendered on the screen Activity View fails to return an XML data layout containing the data for rendering a view Module fails to return a notification object Module does not contain the data needed for the UI display to render the notifications Module fails to return the URL request as a String Module fails to return HTML content Module fails to render web pages corresponding to the user specific action HTML content is not generated HTML content data for the requested MVTS component is not returned as a HTML string Module fails to return an object that contains the necessary information to create an activity view TimeKeepers System Test Plan AC2 AC3 AC4 AC5 AC6 WC1 WC2 RC1 M1 M1 M3 MO1 MO2 G1 PD1 4 9 15 Android DB Controller GCM Receiver Notification Handler Sync Adapter MVTS API Requestor AJAX Handler MVTS Component Controller Remote DB Controller Request Processor API Processor Response Generator OAuth Controller Token Control
47. he ADS and DDS Integration Testing will include following layers Presentation Layer Application Layer Service Layer Data Storage Layer 66 TimeKeepers System Test Plan Volunteer Tracking System 7 1 5 System Validation Testing Phase System Validation Testing will be performed to meet the requirements stated in the System Requirement Specification the acceptance criteria formulated by team and customer 7 2 Tools The team is planning to use the following tools to aid in testing JUnit For unit testing of individual functions and features in the Android App Expresso For testing Android App UI elements PHPUnit For unit testing individual functions and features in the website and backend integration testing Web Component Tester based on Mocha amp Chai For unit testing polymer components GitHub Following the testing at each stage bugs will be reported in the GitHub repository 7 3 Test Metrics Critical Features that are essential to the system 100 lt 100 Any defects that render the system nonfunctional or prevent other tests to run successfully must be fixed immediately High Features that are important to the system gt 90 lt 90 but it can still function without them Any defects that affect the critical functions of the system must be fixed in current release cycle Moderate Features that help polish and refine the gt 75 lt 75 system The system will stil
48. he System If volunteers have committed to an opportunity and it is cancelled the system will notify all volunteers through Email Risk Medium 54 TimeKeepers System Test Plan 5 2 6 5 2 7 5 2 8 4 9 15 Volunteer Tracking System Testing Approach Login to the system as a facilitator Ensure the system allows the deletion of volunteer opportunities Cancel an existing opportunity in the system and ensure that a notification is sent to all volunteers though email Sign Up for Volunteer Opportunities Description The volunteers shall be able to see the details of an opportunity such as the date time and location and have an option to sign up for an opportunity to indicate they will be volunteering at that opportunity Risk Medium Testing Approach Login to the system as a volunteer and click the opportunities page to see the lit of all available opportunities Select and opportunity and sure all the details regarding this particular opportunity is available and the system allows the volunteer to commit to the event Cancel Commitment Description The volunteers shall be able to cancel a commitment they previously made If volunteers previously signed up for an opportunity the system shall allow them to cancel their commitment to indicate they will no longer be volunteering at that opportunity Risk Medium Testing Approach Login to the system as a volunteer and commit to an opportunity Cancel the commitment just made Ensur
49. ich then uses the VTS OAuth subsystem to verify the session before doing any processing After the session has been verified the VTS API which houses all the protocols for data input and retrieval will access the database through the Server Transport The Server Transport acts like the main communication line between the client and the server side to either pass data to the VTS API and VTS OAuth or to send the JSON response back to the Application Layer 2 2 6 Data Storage Layer 22 TimeKeepers System Test Plan Volunteer Tracking System The next layer in our layer hierarchy is the Data Storage Layer This layer consists of the Android and remote databases The Application Layer communicates with the Data Storage Layer through the Service Layer The web application will only communicate with the remote database that will be implemented as a relational MySQL database However the Android application will communicate with both the Android database that will be implemented as relational SQLite database and the remote MySQL database 2 3 Detailed Design Specification This Detailed Design Specification DDS documents the different modules for the Maverick Volunteer Tracking System and the Android app These modules describe the finer details of how the system will be implemented This document will divide each subsystem from each layer into modules and describe the details of how these modules interface with each other or with external services
50. k or it works with major minor issues Therefore we will be utilizing four different types of testing unit testing component testing integration testing and system validation The testing environment with respect to the different tests involved in also crucial Many tests require visual inspection and therefore the team will use different browsers to test the web application and various Android devices to test the Android application Unit Testing Ensures that the lowest level modules explained in the Detailed Design Specification work individually Component Testing Ensures that all the modules work at the subsystem level Integration Testing Ensures that the modules subsystems work together after the integration System Validation Ensures that the system satisfies requirements and acceptance criteria specified and works with minimal issues 10 TimeKeepers System Test Plan Volunteer Tracking System Admin Facilitator Volunteer Android Phone 2 O Internet Personal Computer x Google cloud messaging A Google Cloud Database ls Messaging AP Server Figure 1 1 High Level System Diagram 4 9 15 11 TimeKeepers System Test Plan Volunteer Tracking System 2 Test References This System Test Plan will incorporate previously established documents namely the System Requirement Specification Architecture Design Specification and the Detail Design Specification These documents form the basis for the
51. l function properly without these features The defects can be fixed in the next release cycle Low Features that are listed in future gt 30 lt 30 requirements or are extra add on functionality to existing system Any defects that have little or no impact on the system can be fixed in upcoming future releases Table 7 3 Test Metrics 4 9 15 67 TimeKeepers System Test Plan Volunteer Tracking System 8 Acceptance Criteria This section specifies the acceptance criteria The different tables state the pass and fail criteria for Unit Component Integration and System Validation testing 8 1 Unit Testing Al A2 A3 H P1 WI W2 W3 ACI 4 9 15 UI Display Activity View Notification View Index View Page Router Index View MVTS Pages MVTS Components Activity Controller The different views corresponding to the user action is rendered on the screen The module returns an XML data layout containing all the data for rendering a view by the UI display The module returns a Notification object This object contain all the data needed by the UI display to render the past and new notification Index pointer returns the complete URL request corresponding to the Subdirectory URL request as a String The module returns HTML content corresponding to the URL request which is parsed by the index view module and rendered The module renders the web pages consistently corresponding to t
52. ler GCM Sender PDF Generator The module returns a String array containing data for the requested query The module parses the response and calls the Sync adapter module with the parsed data and initiates a synchronization process via sync adapter The Notification Handler parses the Notification data and returns the notification object to the Notification View The Sync Adapter updates the Android database to synchronize with remote database A JSON Object with all the updated data rows pertaining to the API call is returned The module returns a JSON Response containing the requested MVTS Component data The module returns a formatted JSON response containing all the necessary data to load an MVTS Component in the GUI String array as a result set for the requested SQL query is returned Validated API call request is received back from OAuth controller module A string array containing all the relevant data for that particular API request is returned HTTP response message containing the user action requested data is generated by this module Boolean variable indicating authentication status is returned The module will generates a cookie file containing user session information JSON Object containing information about updated rows in the Remote DB is generated URL for the generated PDF report document is returned Upon entering the URL in a web browser 69 Volunteer Tracking System Module fails to return a S
53. mitment Notify Volunteer Track Progress Generate Reports Customize Preferences Login Logout Register Volunteers Android Application Modules GCM Notification Sync Receiver Handler Adapter X X X X X X X X X X X X X X X Volunteer Tracking System MVTS AJAX MVTS API Handler Component Requestor Controller X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Table 2 10 Application Layer Modules Traceability Matrix 28 TimeKeepers System Test Plan Volunteer Tracking System 2 3 3 3 Service Layer amp Data Storage Layer Req Requirement Modules No Name RDB Request API Response OAuth Token PDF GCM Android Remote Contr Processor Processor Generator Contro Contro Genera Sender Database Database oller ller ller tor 3 1 Input x x x x x x x x Volunteer Hours 3 2 Notify Admin x x x x x x 3 3 Input x x x x x x x Volunteer Hours on behalf of user 3 4 Add Volunteer X x x x x x x Opportunities 3 5 Delete x x x x x x x Volunteer Opportunities 3 6 Sign Up for X X X X X X X Volunteer Opportunities 3 7 Cancel X X X X X X X X Commitment 3 8 Notify X X X X X X X Volunteer 3 9 Track Progress X X X X X X X X 3 10 Generate X X X X X X X X X Reports 3 14 Customize X X X X X X X X Preferences 3 15 Login x x x x x x 3 16 Logout X X X X 3 18 Register X X X X X Volunteers 3 23 Android X X X X X Application Table 2 11 Service Layer and Data Storage Layer Modules
54. n students The source code shall be well documented with comments and details about functionality The code shall help anyone who wants to further develop this product in future Rationale This requirement is not testable 63 TimeKeepers System Test Plan Volunteer Tracking System 6 6 4 9 15 6 5 2 System Maintenance Description The team TimeKeepers shall not be responsible to maintain the system or source code after completion of project The College of Engineering website Developer Christopher Woods will continue to maintain the website as it will be hosted under uta edu engineering Rationale This requirement is not testable Christopher Woods may continue to maintain the system in the future 6 5 3 Training Description The team shall provide training to system manager on how to use and manage the system The team will demo the product upon completion and explain all the functionality of the system which shall help manager to understand system better Rationale This maintenance requirement is not testable Other Requirements 6 6 1 Tablet Support Description The Android app will be available on Android tablets supporting Android version 4 1 2 or higher Rationale This is a future requirement and it will not be implemented in this release 6 6 2 Testing Description The features and functionality of Volunteer Tracking System will be thoroughly tested with all requirements and acceptance criteria before handing
55. n 18 2 2 2 Data Flow Definition iii L SDSU SOS au nn mm a ee 19 22 3 Presentation Layer ais crease sects veces eee NTE 22 2 24 Applicati n Layer EE EE hu EE N EE ER EG 22 2 2 SiS SPVICE AAV EL samikuna ma EG BE DAL AE ER ED EE DR RE GE REG 22 22 0 Data Stora Bayer Aut 22 2 3 Detailed Design Specification u S ee kas N a tt S ee A Ge Ne Ee se ulus 23 2 3 1 Detailed Design Diagram nas RA ee AA ee nn ee ee GR Re RA nan ee ee ee Re ee ee 24 2 32 Produce r Consumer Matrix n u eN vied Se Vee se EO SESSE eeen Ge A ee Ge a Es Ke ge n EE ye sk Eike 25 2 3 3 Requirement Traceability Mallas Ee Ges Rose RS SERE ana RE DE RR iha Dee GODE Gee Ad 27 Si Lest MEA u uu GE OE EE raket 30 RR Ge ama ee ED GE SEG A 30 3 12 Android GUI Unit Tests ui indi han Ee ge DE KOEKE GE De ek eta ek boe snede dwarse 32 3 1 3 Index Pointer Unit Tests vicio ES Ro SEER REK ee ek asan GO ESE SS RAGE SEG ke snee nale eg ke ek sas 33 31 4 Page Router Unit Test 33 3 15 Web GUI Unit Tests aa a R N Ee nd deere heve Belidae wa ap aaa as 34 3 1 6 Android Controller Unit Tests nn RA ee ee asss 35 31 7 Web Controller Unit Tests u n u EE a vie 37 3 1 8 Remote DB Controller Unit TEst u y a nhi Ee RENS RO es qana GR RES Ses De ee aE 38 3 1 9 MVTS API Unit Tests sunset aan 38 31 10 MVTS QAuth Unit Tests iii 39 31 11 GEM sender Unit TES esse A Sa Arie 40 3 112 PDF Generator Unit Tests iii A A 4
56. ning to system Moderate manager on how to use and manage the system The team will demo the product upon completion and explain functionality of the system that shall help manager to understand system better Table 2 5 Maintenance and Support Requirements 4 9 15 16 TimeKeepers System Test Plan Volunteer Tracking System 2 1 6 Others Requirements 8 1 8 2 8 4 8 5 Web Browser Compatibility Web Source Compatibility Responsive Design Testing The web interface shall be accessible via Moderate various popular browsers such as Safari Google Chrome Mozilla Firefox and Internet Explorer All The source code of the web functionality Moderate shall be compatible and portable with various platforms such as Windows Mac and Linux The website shall reflow its layout to fit in for Future the screen resolution or the window size The features and functionality of Volunteer Critical Tracking System will be thoroughly tested with all reguirements and acceptance criteria before handing system to the customers Table 2 6 Other Reguirements 2 2 Architecture Design Specification The Architectural Design Specification ADS documents the design of Maverick Volunteer Tracking System and the Android app ADS provides a concept of the website and the Android app and provides a high level overview and interaction between each layer and their subsystems The test plan is designed to verify each component and the data flo
57. nsure the layout still fits in the current size 4 9 15 61 TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 6 Features Not To Be Tested This section below covers features that will not be tested Some features in this section cannot be directly tested or they may not have been implemented due to time constraints 6 1 Customer Requirements 6 1 1 Generate Newsletter Description The Volunteer Tracking System shall generate a newsletter upon the addition of new volunteer opportunities Rationale This is a future reguirement and it will not be implemented in this version of the release 6 1 2 Generate Appreciation Letter Description When a volunteer reaches a service level the system shall notify the admin This notification will be a system generated notification which they can view on their homepage Upon this notification the admin shall be able to generate a generic appreciation letter for that particular volunteer as a PDF Rationale This is a future requirement and it will not be implemented in this release 6 1 3 Volunteer Stories Description The Volunteer Tracking System shall provide a social aspect to the interface where the volunteers can input and share their stories Rationale This is a future requirement and it will not be implemented in this release 6 1 4 iOS Mobile Application Description The Volunteer Tracking System shall be available in the form of an iOS Application The Applica
58. o and listening results all the user and reguests responding to user reguest To test if the User Input Various actions The High Presentation Click Action will be performed Presentation Layer is on the various Layer displaying all pages to check if should pages for those pages are respond MVTS displaying correct correctly to website and results all the user listening and requests 47 TimeKeepers System Test Plan 13 Application 14 Application I5 Application 16 Service Layer 17 Service Layer 4 9 15 responding to user request To test if the Application Layer is responding to the user request in Presentation Layer To test if the Application Layer is making HTTP request to Service layer and receiving HTTP response from Service layer pertaining to the user request To test if the Application Layer is correctly updating Android Database after updates on Remote Database To test if the user and session is verified before doing any processing for any requests from Application Layer To test if the service layer is responding to the various User Request JSON Request JSON Response GCM API response data and JSON object containing synchronizati on data User and session validation requests JSON Request and API Calls 48 The Application Layer will either stores or retrieves data in the database based on the user request through service layer Various JSON r
59. o a user pressing the notification icon will be used to call the Notification View module Table 3 1 Android GUI Unit Tests 32 The view login home profile etc corresponding to the user action should be rendered on the screen High The module should return an XML data layout containing all the data for rendering a vlew by the UI display The module should return a Notification object This object should contain all the data needed by the UI display to render the past and new notification High Medium TimeKeepers System Test Plan Volunteer Tracking System 3 1 3 Index Pointer Unit Tests The table below describes the unit tests for the different modules in the Index Pointer subsystem Test ID Module Purpose Input Test Detail Expected Priority Result H Index To test ifthe Subdirectory This Index pointer High Pointer index pointer URL module will should return returns the requests be called the complete correct Full with a URL request path URL subdirectory corresponding upon URL to the receiving a request for Subdirectory subdirectory one of the URL request URL request pages in as a String MVTS Table 3 2 Index Pointer Unit Tests 3 1 4 Page Router Unit Tests The table below describes the unit tests for the different modules in the Page Router subsystem Test ID Module Purpose Input Test Detail Expected Priority Result P1 Page Router Totestifthe URL The page The module High page rou
60. ogouts user after clicking logout button System shall register new volunteers The System modifies updates relevant data in the database System notifies user about relevant changes The System modifies updates relevant data in the database 72 Fail Criteria System does not Login System does not Logout System does not register new volunteers System does not update or modify relevant data in the database System does not notify user about relevant changes System does not update or modify relevant data in the database related to adding editing deleting and signing up for opportunities TimeKeepers System Test Plan V6 V7 V8 V9 V10 4 9 15 Generate Ma nage Reports Verify Ease of Use Promote Members De mote Facilitators Verify Web Browser Compatibilit y Verify Android App Availability The System shall generate manage relevant reports The system allows user to reach anywhere on the website with maximum of 3 clicks The System modifies updates relevant data in the database The System is opened in various browsers namely Internet Explorer 10 Safari 6 Google Chrome and Mozilla Firefox Android App is downloaded and installed in Android devices running Android version 4 1 2 Volunteer Tracking System System does not generate relevant reports System takes more than 3 clicks to reach anywhere on the website System does not updat
61. omponent Tests Integration Tests System Validation Tests Risks Test Metrics Unit Testing Acceptance Criteria Component Testing Acceptance Criteria Integration Testing Acceptance Criteria System Validation Acceptance Criteria Test Schedule Approval Signatures Volunteer Tracking System 44 46 47 48 50 52 68 69 73 76 77 82 83 TimeKeepers System Test Plan Volunteer Tracking System 1 1 1 2 1 3 4 9 15 1 Introduction Test Plan Overview The System Test Plan document will provide the detail description of various testing procedures incorporated by the team to ensure that Maverick Volunteer Tracking System meets the requirements listed in System Requirement Specification and acceptance criteria set forth by team and customer as well as to preserve the quality of all components of the product The Test Plan will also make references to previous documents System Requirement Specification Architecture Design Specification and Detailed Design Specification to show the life cycle of development process The document will also Include test items risks features to be tested features to be not tested overall test strategy acceptance criteria test deliverables test schedules and approvals Product Concept In the College of Engineering there is currently an organization Maverick Volunteers which allow the various members of the Board of Advisors to volunteer and participate in different service opportunitie
62. ormed to check if the data is inserted updated de leted successfully in the databases Table 3 18 Integration Tests System validation Testing 3 4 1 Description Volunteer Tracking System Layer with relevant JSON response correspondi ng to the request The Service Layer should successfully insert delete update data in remote database High The Data Storage Layer should store and retrieved properly from Remote and Android Databases High System Validation Testing will be performed to meet the requirements stated in the System Requirement Specification the acceptance criteria formulated by team and customer The test will ensure that layers are communicating with each other and performing the required task 3 4 2 System Validation Test The table below describes the system validation tests for the Maverick Volunteer Tracking System 4 9 15 49 TimeKeepers System Test Plan Verify Login and Logout V2 Register Volunteers V3 Verify input volunteer hours and Track Progress Verify Notification v4 V5 Verify Add Edit Dele te Sign up Opportunities commitment V6 Generate Man age Reports 4 9 15 31 362 3 8 3 4 39 3 6 oo 8 gt gt gt gt gt Username and Password User credential for registration User requests to input number of hours User creating new events or adding volunteered hours User requests
63. parse the response and call the SYNC adapter module with the parsed data and initiate a synchronization process via sync adapter High High High TimeKeepers System Test Plan AC4 Notificati on Handler ACS Sync Adapter AC6 MVTS API Requestor 4 9 15 Notification String data To test if a notification handler passes the notification data to Notification View To test if the Sync Adapter updates the Android database when Remote database is updated JSON object containing synchronizatio n data To test if this module returns a JSON Object containing updated rows in remote DB to Sync adapter JSON Object Table 3 5 Android Controller Unit Tests 36 A test Notification string data will be send to the Notification handler via a test script JSON object containing test synchronizatio n data will be used to call the Sync Adapter module The synchronizatio n data will contain an update request to the remote database A Synchronizati on request will be send to the MVTS API requestor to check for any updated rows in Remote DB Volunteer Tracking System The Notification Handler should parse the Notification data and return the notification object to the Notification View The Sync Adapter should update the Android database to synchronize with remote database Medium High A JSON Object High with all the updated data rows pertaining to the API
64. plication Layer will pass the processed data back to the Presentation Layer which will then be able to display the information back to the user either through the Web GUI or the Android GUI 2 2 4 Application Layer The Application Layer is the next layer in our hierarchy of layers This layer is composed of Android Controller Web Controller and Client Transport subsystems The Application Layer communicates with the presentation layer to get the user input and events associated with user actions Depending on the nature of the input this layer either needs to request information from the database or store data in the database through the Service Layer The Android Controller will be responsible for handling all the events generated by the user through the Android GUI whereas the Web Controller will be responsible for handling all the events generated by the user through the Web GUI The Controller will then pass the data collected to the Service Layer through the Client Transport subsystem The Client Transport acts like a bridge between the Application Layer and the Service Layer 2 2 5 Service Layer The Service Layer is the next layer in our hierarchy of layers The Service Layer is composed of the Server Transport the VTS API VTS OAuth subsystems This layer is responsible for doing all the server side processing and direct database access The Application Layer transfers the data to the server layer through the server transport subsystem wh
65. rd When a user logs in to the system for the first time the system shall allow them to enter their Email for validation When the Email is validated the system shall ask the user to establish their password When a user logs in to the system again they will be reguired to enter their Email and Password for validation 3 16 Logout The Volunteer Tracking System shall allow Critical volunteers to logout of the system When the user is logged out the system shall redirect to the login page 3 18 Register The Volunteer Tracking System shall allow Critical Volunteers Admin to register volunteers and allow access into the system 3 22 Ease of Use The Volunteer Tracking System shall provide a High user friendly interface The system shall also limit the number of clicks to allow a user to reach their desired page easily 3 23 Android The Volunteer Tracking System shall be Low Application available in the form of an Android Application The Application will be available in the Google Play Store to download for free Table 2 1 Customer Requirements 2 1 2 Packaging Requirements 4 1 Website Website will be hosted under a subdirectory of Critical URL http www uta edu 4 2 Page URLs Website URLs will be human readable and search Moderate engine friendly 4 9 15 14 TimeKeepers System Test Plan Volunteer Tracking System 4 3 Google Play Android app will be released into Google Play asa High Publication free download 4 4 Installa
66. s An administrator manually maintains the current system The Maverick Volunteer Tracking System seeks to solve this problem The main purpose of this project is to provide a system to the volunteers in the College of Engineering Board of Advisors to input track and analyze their volunteer activities In addition to the website an Android based mobile app will be developed The purpose of this app is to provide an ease of access to the Volunteer Tracking System The app will allow the volunteers to access the same functionality as the website However the functionality of the Admin and Facilitators is limited To access their unigue functionality an Admin or a Facilitator would need to directly access the website The functionality on the app is limited as the TimeKeepers will be primarily focused on the website In the future the Volunteer Tracking System may be open to students faculty and staff from the College of Engineering or other departments around the campus Product Scope The TimeKeepers are designing a website and an Android application that will provide an efficient and interactive way for the Maverick Volunteers to log their volunteer hours as well as to keep track of their volunteer activities The volunteers will be able to keep themselves updated about the upcoming volunteer opportunities and periodically view their progress report The system will also provide a means to the facilitators to track volunteer participation and use
67. st Fails to display different views corresponding to the user actions Fails to send user input data to the Web Controller Fails to receive HTML content for the specific MVTS components Fails to receive an object that contains the input data Fails to receive an object that contains the necessary information to create an activity view Fails to receive result set from Android Database Fails to update Android Database TimeKeepers System Test Plan AC4 WC1 WC2 RDBC1 MAI MOI PGI GSI ADI RD1 Android Controller Web Controller Web Controller Remote DB Controller MVTS API MVTS OAuth PDF Generator GCM Sender Android Database Remote Database notification about changes in Remote Database The Android Controller receives a JSON Object with result pertaining to the API call The Web Controller formats and relays results back to the user The Web Controller sends a JSON request pertaining to the events generated by user and receive a JSON response corresponding to the JSON request String array as a result set for the requested SQL query is returned The MVTS API responds to the various API calls pertaining to the request and provides the requested data The MVTS OAuth receives either successful user validation or unmatched user credentials URL for the generated PDF report document is returned Upon entering the URL in a web browser the PDF document is open
68. t to the destination Ensure that total number of clicks is less than three 5 2 16 Android Application 4 9 15 Description The Volunteer Tracking System shall be available in the form of an Android Application The Application will be available in the Google Play Store to download for free Risk Medium 57 TimeKeepers System Test Plan Volunteer Tracking System Testing Approach The app will be tapped to open the application and ensure that It launches the system without any issues Navigate through various screens to verify all the options and data is seen properly The specific application functionalities will be tested as described in Customer Reguirements section of this document 5 3 Packaging Requirements 5 3 1 5 3 2 5 3 3 4 9 15 Website URL Description Website will be hosted under a subdirectory of http www uta edu Risk Low Testing Approach Ensure that all files are properly uploaded to the UTA server through a secure port In a browser type in the site address and ensure that it works as expected Page URLs Description Website URLs will be human readable Risk Low Testing Approach Type in a sub URL that directs to another page in the system Ensure that the browser address seen in the website is readable by a member of the team Installation Script Description A PHP installation script that will populate the necessary database tables shall be provided Risk Low Testing Approach
69. tabase SQL lite sets as String query queries will array be corresponding performed to the queries with test should be scripts returned 46 TimeKeepers System Test Plan RD1 Remote Database Volunteer Tracking System To test if data MYSQL Various Result sets as High can be stored database MySQL String array and retrieved query queries will corresponding properly from be to the the remote performed respective database with queries database test should be scripts returned Table 3 17 Data Storage Layer Component Tests 3 3 Integration Testing 3 3 1 Description Integration Testing will be performed to ensure the overall system is functioning after integrating all the modules and components into the layers Integration Testing will verify the functions specified in the ADS and DDS Integration Testing will be conducted at the system level The Systems will be supplied with test data and compared to the expected outcome to ensure that subsystems within the system are functioning together properly and as expected 3 3 2 Integration Test The table below describes the integration tests for the Maverick Volunteer Tracking System I1 Presentation Layer Dn Presentation Layer 4 9 15 To test if the User Tap Various actions The High Presentation Request will be performed Presentation Layer is on the various Layer displaying all pages to check if should pages for those pages are respond Android App displaying correct correctly t
70. tation is in the process of development 5 1 2 Medium This feature s process of implementation is established but is still undergoing development 5 1 3 Low This feature s has been accurately functioning during the stage II of the prototype phase of development and testing 5 2 Customer Requirements 5 2 1 Input Volunteer Hours Description The Volunteer Tracking System shall allow a user to input the hours volunteered To input the hours the volunteers shall be able to select the name of the opportunity from a dropdown associated with a category and enter the number of hours they volunteered along with comments If a volunteer does not commit to an opportunity but still volunteers at that opportunity the system shall allow them to input the hours they volunteered Risk Medium Testing Approach Login to the system as a volunteer and input volunteer hours to ensure the data in terms of number of hours volunteered is correctly analyzed by the system Also ensure that no commitment is given to an event but the user is still able to enter the number of hours they volunteered 53 TimeKeepers System Test Plan 5 2 2 5 2 3 5 2 4 5 2 5 4 9 15 Volunteer Tracking System Notify Admin Description The Volunteer Tracking System shall also notify the admin and the opportunity category facilitator when members input their time volunteered This notification will be system generated The admin and the facilitator will be able to
71. tem Test Plan Volunteer Tracking System 2 1 5 Maintenance and Support Requirements 7 1 Source Code All the documentation prepared by team Moderate Documentation A TimeKeepers including System Requirements vailability Specification Architectural Design Specification Detail Design Specification and System Testing Plan will be made available to future senior design students The source code shall be well doeumented with comments and details about functionality The code shall help anyone who want to further develop this product in future 7 2 Password The team TimeKeepers shall not be responsible Critical Encryption to maintain the system or source code after completion of project The College of Engineering website Developer Christopher Woods will continue to maintain the website as it will be hosted under uta edu engineering 7 3 PHP Version The UTA servers are running PHP version 5 1 Critical Support Therefore the web application shall be compatible with PHP version 5 1 7 4 Android Version The mobile version of the system will be Low Support Android based The application will support a minimum API level of 16 which corresponds to version 4 1 2 Jelly Bean 7 5 User Manual The team will provide user manual that Moderate describes the different functionality of product and instructions on how to use product This user manual shall support system administrator for any problems in future 7 6 Training The team shall provide trai
72. ter reguest router should return returns the module will HTML relevant be invoked content HTML witha URL corresponding content to the request for to the URL index view a HTML request which page can be parsed by the index view module and rendered Table 3 3 Page Router Unit Tests 4 9 15 33 TimeKeepers System Test Plan 3 1 5 Web GUI Unit Tests Volunteer Tracking System The table below describes the unit tests for the different modules in the Web GUI subsystem W1 W2 W3 4 9 15 Index View MVTS Page MVTS Component To test if User the web input click interface is action displayed consistently HTML import request To test 1f the MVTS Page can combine all the MVTS Components and return it as an HTML content to the page router To test 1f the MVTS Component can return the HTML component requested from the MVTS Page HTML import request The user will interact with the web interface through the various buttons and forms in the display HTML import request for an MVTS Page will be sent to this module through a test script HTML import request for a MVTS Component will be send to the MVTS Component module through a test script Table 3 4 Web GUI Unit Tests 34 The module should render the web pages consistently corresponding to the user specific action High Combined HTML content containing all the requested MVTS Component will be generate
73. the facilitator will be able to see this notification on their home page The Volunteer Tracking System shall allow users to track progress of their volunteer activities and the status of different service levels Service levels are different levels that volunteers can achieve based on the total number of hours The levels are divided as follows 30 60 90 150 and 150 The Volunteer Tracking System shall generate progress reports for each volunteer upon their request The progress report should include details such as the categories types of opportunities volunteered in and the total number of hours volunteered The Volunteer Tracking System shall allow admin to send progress reports along with comments and attachments to the specified users The Volunteer Tracking System shall allow admin to designate or promote a member to a facilitator 13 High High High High Critical High Moderate Moderate TimeKeepers System Test Plan Volunteer Tracking System 3 13 Demote The Volunteer Tracking System shall allow Moderate Facilitators admin to demote a facilitator to a member 3 14 Customize The Volunteer Tracking System shall allow High Preferences volunteers to customize their preferences Preferences include setting the date of availability along with level of interest in different opportunity categories 3 15 Login The Volunteer Tracking System shall allow Critical users to login with their Email and passwo
74. tion A PHP installation script that will populate the Low Script necessary database tables shall be provided Table 2 2 Packaging Requirements 2 1 3 Performance Requirements 5 1 Application Response time between user interaction and Moderate Response Time result should be less than 8 seconds in both the website and the Android app 5 2 Dynamic Page Only the necessary parts of the web page Moderate Update will be updated upon the user Interaction instead reloading the page completely 5 3 File Compression JavaScript and CSS files will be compressed Low to reduce the file size Size of JPEG images should be less than 3 MB 5 4 Third Party JavaScript and CSS libraries will be directly Low Libraries and accessed from the CDN servers thereby Frameworks improving the access time in distant locations 5 5 Serve Scaled Differently scaled images will be used in Low Image different scenarios i e thumbnails full screen images Table 2 3 Performance Requirements 2 1 4 Security and Privacy Requirement 7 1 Website Cache Age of the website cache will be restricted to 7 Low days 6 2 Password All user password shall be encrypted in the Critical Encryption MySQL database 6 3 Malicious Input System shall validate all the input data to ensure Moderate Protection that the entered data is correct and or user has not entered any malicious code in any input fields Table 2 4 Security and Privacy Requirements 4 9 15 15 TimeKeepers Sys
75. tion will be available in the App Store to download for free Rationale This is a future requirement and it will not be implemented in this release 62 TimeKeepers System Test Plan Volunteer Tracking System 4 9 15 6 2 6 3 Performance Requirements 6 2 1 Third Party Code Libraries and Frameworks Description JavaScript and CSS libraries will be directly accessed from the CDN servers thereby improving the access time in distant locations Rationale This feature is not testable When retrieving third party code libraries the performance time depends on the response it receives from the third party servers Security and Privacy Requirements 6 3 1 Website Cache Description Age of the website cache will be restricted to 7 days Rationale Due to time constraints this reguirement will not be tested 6 4 Packaging Requirements 6 4 1 Google Play Publication Description Android app will be released into Google Play as a free download Rationale No test is needed for the requirement If it passes Google s quality assurance process of app publishing then it will be published 6 5 Maintenance and Support Requirements 6 5 1 Source Code Documentation Source Code Availability Description All the documentation prepared by team TimeKeepers including System Requirements Specification Architectural Design Specification Detail Design Specification and System Testing Plan will be made available to future senior desig
76. tring array containing data for the requested query Module fails to parse response Fails to call the Sync Adapter module with the parsed data Fails to initiate a synchronization process via the sync adapter Fails to parse the notification data Fails to return the notification object to the notification view Fails to update the android database sync with remote database Fails to return the JSON Object containing updated rows Fails to return a JSON response containing the requested MVTS component data Fails to return a formatted JSON response containing all the necessary data Fails to return String array as a result set Fails to receive the validated API call from the OAuth Controller Fails to return the string array containing all the relevant data Fails to generate a HTTP response containing the user action requested Fails to return a Boolean variable Fails to generate a cookie file containing user session information Fails to generate the JSON object that contains information about updated rows Fails to generate URL for the PDF URL is incorrect TimeKeepers System Test Plan AD1 RD1 Android Database Remote Database the PDF document is opened SQL lite result sets as String array corresponding to the queries is returned Result sets as String array corresponding to the respective queries is returned Volunteer Tracking System Fails to return result sets as String array Fails to re
77. turn result set as String array Table 8 1 Unit Testing Acceptance Criteria 8 2 Component Testing AGI AG2 IP1 PRI WGI WG2 WG3 ACI AC2 AC3 4 9 15 Android GUI Android GUI Index Pointer Page Router Web GUI Web GUI Web GUI Android Controller Android Controller Android Controller The Android GUI displays different views corresponding to the user actions The Android GUI relays user input data to Android Controller Index pointer returns the complete URL request corresponding to the Subdirectory URL request as a String The Page Router returns HTML content corresponding to the URL request The Web GUI displays different views and results corresponding to the user actions The Web GUI relays user input data to Web Controller The Web GUI receives all the MVTS components in the form of HTML content needed for each specific page The Android Controller receives and returns an object to containing all the necessary information to create an activity view The Android Controller receives result set from Android Database depending on the request The Android Controller updates Android Database upon receiving 70 Fails to display different views corresponding to different actions Fails to pass input data to Android Controller Fails to return URL as a String corresponding to the Subdirectory URL Fails to return the HTML content corresponding to the URL reque
78. uld include details such as the categories types of opportunities volunteered in and the total number of hours volunteered Risk Medium Testing Approach Login to the system as a volunteer and click the generate report button Open the report and ensure that all details such as categories of volunteer opportunities and total number of hours volunteered are included 5 2 11 Customize Preferences Description The Volunteer Tracking System shall allow volunteers to customize their preferences Preferences include setting the date of availability along with level of interest in different opportunity categories Risk Medium Testing Approach Login to the system as a volunteer and click on the profile tab Select customization options and set preferences to include the dates of availability and rank the level of interest in certain categories Ensure that the system is generating a new notification based on the possible matches 5 2 12 Login 4 9 15 Description The Volunteer Tracking System shall allow users to login with their Email and password When a user logs in to the system for the first time the system shall allow them to enter their Email for validation When the Email is validated the system shall ask the user to establish their password When a user logs in to the system again they will be required to enter their Email and Password for validation Risk Medium 56 TimeKeepers System Test Plan Volunteer Tracking System
79. ving notification about changes in Remote Database The Android Controller should receive a JSON Object with result pertaining to the API call High High The Web Controller Should convert JSON response to HTML content and relay results back to the Web GUI The Web Controller should successfully responds to all the events generated by user through High High TimeKeepers System Test Plan MVTS API Table 3 15 Application Layer Component Tests 3 2 4 Service Layer Component Test Volunteer Tracking System Web GUI and relay it to the MVTS API The table below describes the component tests for the different subsystems in the Service Layer RDBC1 MA1 MO1 4 9 15 Remote DB Controller MVTS API MVTS OAuth To test if SQL queries can be performed to the Remote database To test if the MVTS API is fetching the required data from the Remote Database and fulfilling the API request coming from the Application layer To test if MVTS OAuth validates the user and session Parsed String data for creating SQL queries API response and String Array User and Session validation request 45 Sample string array containing data for SQL queries will be send to the various database access methods Various API calls pertaining to the request from Android and Web Controller subsystem will be made to check if MVTS API is responding correctly User
80. ws between them In order to ensure that the system functions properly and that it is producing acceptable results the team must test these components to verify that each one is working as it should and that the interactions between the components are behaving correctly 4 9 15 17 TimeKeepers System Test Plan Volunteer Tracking System 2 2 1 Architecture Design Diagram Volunteer Presentation Layer Android Controller Controller GCM1 cm AC cra WE Client Transport _ RD1 Application Layer ST2 Server Transport s CT3 GE Remote DB Controller Service VO2 NAN Layer RDC1 MVTS OAuth MAT MVTS API VA2 VA4 vaa ps GCM Sender PDF Generator Data Storage Android Layer Database AD1 AC3 External Services GCM API Internet Remote Database Figure 2 2 Architecture Diagram 4 9 15 18 TimeKeepers System Test Plan 4 9 15 2 2 2 ACI AC2 AC3 ADI AF1 AGI AG2 cri CT2 CT3 GCMI GCMS1 IP1 Data Flow Definition The Android Controller will relay what needs to be displayed to the user in the Android GUI The Android Controller will format and send user input data to the Client Transport which will then be processed by the Service Layer The Android Controller will input formatted user input data Into the Android Database The Android Controller will read data from the Android Database The Admin Facilitator will input data into

System Test Plan (Maverick Volunteer Tracking System)

Contents

Download Pdf Manuals

Related Search

Related Contents