for A-plus Writer peer review Test Plan

SW-MTP-001

This is the Master Test Plan for the Android based SoundWave Application project. This plan will cover those items and elements directly and indirectly related to the operation and functionality of the application. Its focus is to ensure that the SoundWave Mobile application and the associated Web-based application functionally operate at a level acceptable to the design and scope originally envisioned while leaving room for enhancements and improvements to further increase functionality and security.

The project will consist of the following test plans whose details are outlined in Section 08 of this document and further defined throughout:

· Application (Mobile App and Web App)

· System/Integration & Acceptance

This 8 week course provides for a strict project timeline with the first three weeks being dedicated to introductions, group formation and project planning. The final week is dedicated to peer review. This leaves 4 weeks for development and testing; dictating that much of the testing will be performed in parallel with development. However, acceptance testing will be primarily reserved for the final week of the 4 week period. There will be little if any time for plan deviation or adding of additional features. Provided time permits for the latter, additional formalized testing plans will not be incorporated except as they apply to the functionality of the project to ensure no negative aspects have been introduced in regard to meeting the original project objectives.

The following items are to be tested:

· SoundWave Mobile Application

· SoundWave Web-based Application

NOTE: Test Harness creation

In the process of testing the application an html based webpage utilizing JavaScript may be used as a test harness. The interface may be utilized in order to generate requests, and to modify the parameters of those requests. This will save the tester time when attempting to test various request cases.

This interface may also provide a plain text display area for validation of any text or application JSON (JavaScript Object Notation) which is returned from the web server. This test harness is to be used for validation of the external responsiveness of the application API interface. This test harness can be used in the integration test phase, after the server side code has been unit tested.

There are a number of critical areas and operational risks associated with this project, some of which are outside the control of the applications involved. Therefore all of these areas must be verified to conform to a minimal or acceptable level of performance.

A. Launching and closing the application: The user should be able to repeatedly launch and close the application on their mobile device without utilizing unnecessary resources or leaving residual elements within the system after being closed that may cause system instability or crashes.

B. User Registration: The registration of a user from a mobile device should properly update the registration database. The user registration must be validated against duplication of critical PII within the registered user database.

C. Registration List and Contact List: The registration database itself will be housed on a separate server maintained by a third party. Appropriate availability, backup and recovery of the server and data must be verified.

D. Sound File recording, compression and playback: The user should be able to successfully record a message from their mobile device when selecting a contact from their contact list. Compression of that audio for transmission purposes should minimize quality playback issues and should not introduce corrupted files.

E. Sound File sending and receiving: Audio files should distribute freely and successfully across the SoundWave application system with minimal delay. Wireless carrier network reliability should be verified to distribute audio files without interference from traffic prioritization patterns or other issues that may cause the files to be delayed or become blocked unnecessarily or beyond a reasonable scope.

The following is a list of features that will be the focus of the test plan during testing of the application system:

A. New or Modify User Registration

B. Add & Delete Contact

C. Send & Receive Audio File (i.e. recording and playback)

The following is a list of features that will not be specifically addressed during testing of the application system. Indirect testing efforts will encapsulate these areas and serve to prove their functionality:

A. Registered User Database

B. Audio File Cloud Storage Server

C. Audio File Metadata Database

The following are the tests to be performed both during and after the development cycle of the entire system application to ensure that all project deliverables have been met. These tests will also indirectly ensure that the application databases and cloud server operate as required by pulling information from and storing information to them.

The following test cases will ensure the operation of the Android mobile application performs as expected.

Lightweight Requirements List

General

REQ-SWV-001 An Android application named SoundWave SHALL be created.

REQ-SWV-002 SoundWave SHALL support Android Operating System 4.0 and greater.

REQ-SWV-003 SoundWave MAY support Android OS 2.3 and greater.

Sound Recording

REQ-SWV-004 SoundWave SHALL have the ability to record and save sound files.

REQ-SWV-005 SoundWave MAY have the ability to stream audio to another client application in near-real time.

Connectivity

REQ-SWV-006 SoundWave SHALL allow for recorded sound files to be posted to a web application.

REQ-SWV-007 SoundWave SHALL include envelope information to be included in files posted to the web application (see REQ-SWV-006).

REQ-SWV-009 SoundWave SHALL be capable of downloading sound files from a web application.

REQ-SWV-010 SoundWave SHALL maintain a connection with the web application and react in near-real time to incoming messages.

REQ-SWV-011 Near-real time SHALL be defined as less than 10 seconds for the purposed of the SoundWave application.

REQ-SWV-012 SoundWave SHALL communicate with the web application via HTTP.

User Configuration

REQ-SWV-013 SoundWave SHALL allow the user to configure contacts.

REQ-SWV-014 SoundWave contacts SHALL consists of a display name and email address.

REQ-SWV-015 SoundWave contacts email addresses SHALL be used to uniquely identify other users of the application.

REQ-SWV-016 SoundWave contacts SHOULD be customizable with a picture associated with the contact.

REQ-SWV-030 SoundWave SHOULD provide a configuration option to store queued sound message or play them as they arrive.

EQ-SWV-017 SoundWave SHALL support a simple password authentication system.

User Interface

REQ-SWV-018 SoundWave SHALL implement a simple user interface which displays configured contacts.

REQ-SWV-019 SoundWave SHALL allow users to long hold on contacts configured in the user interface to record and transmit sound files to the selected contact.

REQ-SWV-020 SoundWave record and transmit actions SHALL take no more than one UI press and release.

REQ-SWV-021 Messages waiting in the SoundWave application SHALL be clearly visible in the user interface for the associated contact.

Test Specifications and Procedures for Android Application

Test Name: AAT-01: Send a sound message

Description: Transmit a sound message to a user with SoundWave main screen.

Requirement(s): SWV-REQ 006, REQ-SWV-019, REQ-SWV-020

Prerequisites: The user is a registered SoundWave user with registered contacts already configured.

Setup: Install SoundWave on an Android phone. Follow account registration and contact creation test plans to configure multiple contacts.

Steps:

Test Name: AAT-02: Listening to a sound message Queued Mode

Description: This test case describes the act of listening to a sound message from another user with SoundWave. The message is received while the receiving user does not have the SoundWave application running in the foreground of the phone so the message is queued for playback.

Requirement(s): SWV-REQ 009, REQ-SWV-019, REQ-SWV-020

Prerequisites: Two android phones with SoundWave are required. The users are a registered SoundWave user with registered contacts already configured.

Setup: Install SoundWave on two Android phones. Follow account registration and contact creation test plans to configure multiple contacts. Both phones should have a registered contact for the account associated with the other phone. Label one Phone A and one Phone B.

Steps:

Test Name: AAT-03: Listening to a sound message Near-real-time Mode

Description: This test case describes the act of listening to a sound message from another user with SoundWave. The message is received while the receiving user has the SoundWave application running in the foreground of the phone so the message played immediately.

Requirement(s): SWV-REQ 009, REQ-SWV-019, REQ-SWV-020

Prerequisites: Two android phones with SoundWave are required. The users are a registered SoundWave user with registered contacts already configured.

Setup: Install SoundWave on two Android phones. Follow account registration and contact creation test plans to configure multiple contacts. Both phones should have a registered contact for the account associated with the other phone. Label one Phone A and one Phone B.

Steps:

The following test cases will ensure the operation of the web-based application performs as expected.

Test Specifications and Procedures for Web Application: User Integration

Test Name: WAT-01-UI: getInfo general

Description: Testing getinfo() function of the REST interface web application. This function will be used to retrieve all information from the web application. It will be used during user registration to verify that the email is unique, and then to register the user with user with appropriate information, also to add contacts, and get and store message data.

(e.g. http://application.com/getUserInfo?user=12345)

Requirement(s): Information is retrievable from the web application.

Prerequisites: Android application is connected to web server through REST interface and data exists in appropriate database tables.

Setup: Query the database table directly to get desired information.

(e.g. SELECT * FROM (Table) WHERE (Field)=X)

Steps:

Test Name: WAT-02-UI: getUserInbox external

Description: A get Inbox Info request is made.

(e.g. http://application.com/getUserInbox?user=12345)

Requirement(s): User inbox info is retrievable from the web application

Prerequisites: The user database table is accessible.

Setup: Query the database table directly to prove the test case.

(e.g. SELECT * FROM inboxTable WHERE user=12345)

Caveats: Security for this feature IS NOT a requirement and thus will not be tested. More specifically, inbox information for any user can be retrieved from the API if the user ID is known.

Steps:

Test Name: WAT-03-UI: getMessage external

Description: A get message request is made.

For example (http://application.com/getMessage?message=12345

Requirement(s): Message info is retrievable

Prerequisites: The message info exists in the appropriate database table and points to the appropriate file.

Setup: Have a pre-set message to be returned via the query, know the format and contents of the voice message.

Caveats: Security for this feature IS NOT a requirement and thus will not be tested. More specifically, message information for any user can be retrieved from the API, if the message id is known.

Steps:

Test Specifications and Procedures for Web Application: Unit Testing

Test Name: WAT-01-UT: message storage / database update test.

Description: Testing the storing of a message into cloud storage and database.

Requirement(s): User info is retrievable. Message info is retrievable. Database tables are writable. Cloud storage directories are writable.

Prerequisites: The sending user and target user(s) exist.

Setup: Create an audio file.

Steps:

For this project, System and Integration testing is virtually identical to Acceptance testing and therefore shall be performed as a singular testing requirement.

Test Specifications and Procedures for User Acceptance Testing

Test Name: UAT-01: User Registration

Description: User registers their email address with SoundWave using the Android App.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet.

Prerequisites: User has a valid email address.

Setup: Tester must verify that a valid internet connection exists; and that the user has a valid email address.

Steps:

Test Name: UAT-02: Add Contact

Description: User adds a contact to their account.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet.

Prerequisites: User's intended contact has a registered email.

Setup: Tester must verify that a valid internet connection exists; and that the intended contact's email is already registered.

Steps:

Test Name: UAT-03: Send Message

Description: User sends a message to one of their existing contacts.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet. Device has a functioning microphone.

Prerequisites: User has at least one valid contact.

Setup: Tester must verify that a valid internet connection exists; that the User has at least one valid contact; and the device has a functioning microphone.

Steps:

Test Name: UAT-04: Listen to Received Message

Description: User plays/listens to a message they have received.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet. Device has functioning speakers.

Prerequisites: User has at least one received message and system displays a number on the user's contact who has sent a message to the user.

Setup: Tester must verify that a valid internet connection exists; that the device has functioning speakers; and the User has at least one received message (may need to be sent by the tester).

Steps:

Test Name: UAT-05: Delete Contact

Description: User deletes an existing contact.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet.

Prerequisites: User has at least one contact.

Setup: Tester must verify that a valid internet connection exists; and the User has at least one contact.

Steps:

Test Specifications and Procedures for Operational Acceptance Testing

Test Name: OAT-01: Automated mass user registration

Description: Test runs script to register 100 - 1000 Users in quick succession.

Requirement(s): SoundWave is installed on mobile device running Android. Device is connected to the internet.

Prerequisites: Testing script installed on test device.

Setup: Tester must verify that a valid internet connection exists; and that the script is initiated properly.

Steps:

The following is a list of items to be delivered as part of this plan.

· Application Test Plan (Mobile Application and Web Application)

· System/Integration & Acceptance Test Plan

Below is list of the required tasks for this test plan and their status:

The following elements are required to support the overall testing effort at all levels of the Android SoundWave Application project:

A. Access to mobile devices with Android OS 4.0 or later installed. Devices down to Android OS 2.3 should be able to install and utilize the application. However, these devices will not be fully supported by the application software. Each device needs to have an active data plan or internet access and be capable of 512Kbps internet speeds.

B. Access to fully managed internet based server system capable of operating PHP and / or Java servlets and MySQL version 5.5 or higher. The minimum system requirements for the server are as follows:

C. Access to a cloud server, the database management system, registered user database and the sound file database housed on the server.

Staffing for the team consists of the seven project participants detailed on the cover of this document. Each team member comes with a variation of skill sets acquired from multiple sources consisting of curriculum, job requirements and personal knowledge. Team members will be leveraged for their strengths to lead aspects of the project well suited for their knowledge base and will be tasked to train and/or assist other team members in these areas when needed. Outside of any expertise for specific development and testing processes, team members will be expected to obtain requisite knowledge and training on their own initiative in order to ensure project success.

The team is led by Joseph Keefe and decisions regarding the project will be decided by the entire project team, as listed in the approvals section. Decisions will move forward with the unanimity of the project team and in some instances simple majority agreement. In the event that consensus is elusive, the team lead (project manager) will be the deciding factor.

Responsibilities for the team are aligned with scheduling and are detailed below. The 4 week development and testing period is outlined and as stated many aspects of testing detailed in this test plan will be performed in parallel with the development cycle. Also keep in mind that responsibilities are tentative and subject to change based on need, timelines, skill-sets and availability:

Minimal risk is associated with this project as external resources that have been chosen are highly reliable and have high availability. In the event that these resources become unavailable for unforeseen reasons, others will be chosen, with negligible or minimal impact to project deliverables, as there are multiple external resource options to choose from that will accommodate the project and its features.

The following individuals are responsible for approving project procession and completion.