Test Plan

COP4331 Processes in Object-Oriented Programming | Fall 2014 | Group 12 - Project 17

Modification history:

Team Name: The Spungos' Turbo Wallhacks

Team Members:

• Alex Berliner; alexberliner@knights.ucf.edu
• Christopher Kovaleski; ckovaleski@knights.ucf.edu
• Oscar Hedblad; oscarhedblad@gmail.com
• Luis Duque; luisduque23@gmail.com
• Alan Birmaher; abirmaher@knights.ucf.edu
• Jimmie Potts; jimmie.potts@knights.ucf.edu

Contents of this Document

1. Introduction:

Overall Objective for Software Test Activity

Reference Documents

2. Description of Test Environment
3. Overall Stopping Criteria
4. Description of Individual Test Cases

SECTION 1: Introduction

Our overall objective for Software Test Activity is to find and address the issues that need attention by way of internal testing followed by external beta testing. These tests will help us determine the repairs and changes that need to be made in the following areas:

• Software bugs, issues that cause the application to fail in any way.
• Security, check for weaknesses in this area.
• Ease of use, check for ease of use primarily during beta testing.
• Usefulness/ practicality, find out if the application is ultimately beneficial to the end user.

Reference Documents:

• Concept of Operations: http://www.cs.ucf.edu/courses/cop4331/fall2014/cop4331-12/artifacts/ConOps.html
• Project Plan: http://www.cs.ucf.edu/courses/cop4331/fall2014/cop4331-12/artifacts/ProjectPlan.html
• SRS: http://www.cs.ucf.edu/courses/cop4331/fall2014/cop4331-12/artifacts/SRS.html
• Software Engineering: Theory and Practice. Pfleeger, Atlee. Fourth Edition, Pearson.

SECTION 2: Description of Test Environment

Our testing will take place on various different Android devices in order to verify that the application works correctly on different devices. Our testing will have multiple stages. The first phase will consist of developer/ internal testing. We will use this time to clean up and optimize the software to the best of our abilities before moving to the beta testing phase. During this phase we will continue testing internally, but we will allow individuals from outside the team to test. This will help us by exposing the application to a larger spectrum of device and software combinations to run on, giving us the best chance of eliminating the maximum amount of issues before release.

SECTION 3: Stopping Criteria

The following criteria will be examined with regards to testing and when to cease testing and development:

• Bugs: These issues will be noted as they are incurred. Every 1- 2 weeks we will work on the bugs we have found and fix the code.
• Major Bugs: For more extreme bugs which hinder the usability of the program for other testing we will take these issues under advisement and assess them immediately in order to continue testing our application.
• Improvements: As we test the software and find features that could imporve our application we will take note of these and before doing out code updated every 1- 2 weeks we will discuss the possibility of adding these features to our code as well. If the team decides to implement the changes then they will be coded in.
• Stop Development: For this to take place all beta testers must be able to complete a list of use cases with no issues as well as adding their own use cases by just using the application. The testers must be able to complete 10 successful send/ receive challenges each via different social networks to different people in order to test all facets of the software and verify their correctness. Once these criteria have been met, then the development is complete and we can move forward with the application.

SECTION 4: Description of Individual Test Cases

Initiate Challenge to individual via Twitter:

• Test Objective: The goal of this test is to confirm that a user is able to successfully send a challenge to another user via Twitter.
• Test Description: For these tests we will be posting from an Twitter account created for testing specifically in order to track our results. For the testing, the test devices will have the video at this link saved locally and will use this video for testing purposes (https://www.youtube.com/watch?v=eoLGOM671_0). Challenges will be sent to other test accounts created and eventually when we move to beta testing, we will move to allowing users to test with their own accounts to other friends with the application with their own media.
• Test Conditions: See Test Environment section above.
• Expected Results:
• Expected Results: The result will be the creation of a post to the user's Twitter with a friend tagged for the challenge to which you are challenging them. This post will be a video with a caption in this format, “Completed #XXXXXXXXXXXXXXXChallenge: @XXXXXXXXXXXXXXX must complete in X days, and challenge X friends! #CYF”

Initiate Challenge to group via Twitter:

• Test Objective: The goal of this test is to confirm that a user is able to successfully send challenges to multiple user via Twitter.
• Test Description: For these tests we will be posting from an Twitter account created for testing specifically in order to track our results. For the testing, the test devices will have the video at this link saved locally and will use this video for testing purposes (https://www.youtube.com/watch?v=eoLGOM671_0). Challenges will be sent to other test accounts created and eventually when we move to beta testing, we will move to allowing users to test with their own accounts to other friends with the application with their own media.
• Test Conditions: See Test Environment section above.
• Expected Results:
• Expected Results: The result will be the creation of a post to the user's Twitter with friends tagged for the challenge to which you are challenging them. This post will be a video with a caption in this format, “Completed #XXXXXXXXXXXXXXXChallenge: @XXXXXXXXXXXXXXX must complete in X days, and challenge X friends! #CYF”

Respond to Challenge and challenge one user via Twitter:

• Test Objective: The goal of this test is to confirm that a user is able to successfully respond to a challenge and send it along to a single user via Twitter.
• Test Description: For these tests we will be posting from an Twitter account created for testing specifically in order to track our results. For the testing, the test devices will have the video at this link saved locally and will use this video for testing purposes (https://www.youtube.com/watch?v=eoLGOM671_0). Challenges will be sent to other test accounts created and eventually when we move to beta testing, we will move to allowing users to test with their own accounts to other friends with the application with their own media.
• Test Conditions: See Test Environment section above.
• Expected Results:
• Expected Results: The result will be the creation of a post to the user's Twitter with a friend tagged for the challenge to which you are challenging them. This post will be a video with a caption in this format, “Completed #XXXXXXXXXXXXXXXChallenge: @XXXXXXXXXXXXXXX must complete in X days, and challenge X friends! #CYF”

Respond to Challenge and challenge multiple users via Twitter:

• Test Objective: The goal of this test is to confirm that a user is able to successfully respond to a challenge and send it along to multiple users via Twitter.
• Test Description: For these tests we will be posting from an Twitter account created for testing specifically in order to track our results. For the testing, the test devices will have the video at this link saved locally and will use this video for testing purposes (https://www.youtube.com/watch?v=eoLGOM671_0). Challenges will be sent to other test accounts created and eventually when we move to beta testing, we will move to allowing users to test with their own accounts to other friends with the application with their own media.
• Test Conditions: See Test Environment section above.
• Expected Results:
• Expected Results: The result will be the creation of a post to the user's Twitter with friends tagged for the challenge to which you are challenging them. This post will be a video with a caption in this format, “Completed #XXXXXXXXXXXXXXXChallenge: @XXXXXXXXXXXXXXX must complete in X days, and challenge X friends! #CYF”

Template created by G. Walton (GWalton@mail.ucf.edu) on March 28, 1999 and last modified on August 15, 2000

This page last modified by Alan Birmaher on 11/16/14