test plan

Testing Goals and Strategies

First and foremost, our goal is to make this app as simple as possible. Due to the nature of its use, our users will be very dizzy and disoriented while using our app. Therefore, we need to simplify the movement through our app as much as possible, so as to create the best user experience. Throughout testing, we will constantly refine the UI to eliminate any parts that our test users find difficult to interact with or understand. In order to test this, we will first test our app on our client’s colleagues, who are familiar with the process, and not suffering from the symptoms of BPPV while trying to interact with the app. If they think certain parts need to made clearer, then we can be sure that a patient with less knowledge will definitely need it to be simplified.

Another big goal of our testing will be to ensure that our app’s calibration is accurate. For this maneuver to work properly, the movements must be performed very specifically. As of right now, we have the app working based on calculations made by our team for each degree of movement needed, as specified by our client. However, this does not always prove to be the perfect position in practice. The maneuver is slightly reliant on the individual patient, as different body shapes and sizes cause slight differences in the angles when the patient lays back. Therefore, we will use multiple testers to refine this by aggregating the data from their tests and refining the algorithm for detecting what is considered a correct movement. While we are refining this algorithm, we will have patients come in and do the maneuver while still being observed by the doctor, which will ensure that they still receive the correct treatment. However, it will allow us to see how well our app lines up with what the doctor is explaining to the patient, and give us a good read on how well we have calibrated our app.

Resources

For our testing to work as well as it can, we will definitely want to create data files that track each patient’s movements throughout the app, as well as send out a survey that allows patients to give us feedback on their experience with the app. Within our app, we can build the functionality to send back user data on the accelerometer information, and we can set up a simple google form link at the end of the treatment steps. Therefore, we need no external resources in order to test our app with users.

Deployment

We hope to get the MVP version of our app out on the app store by the end of October, which will ensure that we always have a stable version of the app that is available to demo. Furthermore, this will allow us to expand our testing to include many more people than would be possible if we simply had a test phone that we had to leave with our client. We have begun researching the steps required to get an app on the App Store, and we feel confident we will be able to get it up to the right standard in time. Then, we can only release a new version of the app when we have fixed certain things and made sure they are stable.

Test Scenarios

Test ID: 001

Feature: Treatment Steps

Purpose: Test the progression of the treatment steps when the user is correctly lined up.

Pre-Conditions: Beginning of the treatment steps.

Steps: Have a user click start and line the app up correctly so that the treatment is able to progress.

Post-Conditions: Completed the treatment.

Test ID: 002

Feature: Treatment Steps

Purpose: Ensure that the progress bar stops if the user strays too far from the correct spot.

Pre-Conditions: The app is lined up correctly.

Steps: Have a user line the app up incorrectly and confirm that the treatment stops.

Post-Conditions: The timer does not continue increasing.

Test ID: 003

Feature: Treatment Steps

Purpose: Make sure that the time designated at each step is enough time for the treatment to work effectively.

Pre-Conditions: The user is suffering from BPPV.

Steps: Have the user proceed through all of our treatment steps.

Post-Conditions: The user’s symptoms are fixed.

Test ID: 004

Feature: Accelerometer Data

Purpose: Work on perfecting our accelerometer readings and assumptions for what constitutes a correct movement.

Pre-Conditions: Set up the app with the basic angle assumptions.

Steps: Have a group of doctors first check our angle assumptions with what they would advise for a patient.

Post-Conditions: Have a more refined algorithm, and more understanding of the amount of leeway given in the maneuver.

Test ID: 005

Feature: Accelerometer Data

Purpose: Work on perfecting our accelerometer readings and assumptions for what constitutes a correct movement.

Pre-Conditions: A basic understanding of how the movements work and what the angles should be.

Steps: Let doctors run through the app themselves and see how the accelerometer feels.

Post-Conditions: Have a more refined algorithm, and more understanding of the amount of leeway given in the maneuver.

Test ID: 006

Feature: Accelerometer Data

Purpose: Work on perfecting our accelerometer readings and assumptions for what constitutes a correct movement.

Pre-Conditions: A good algorithm based on the feedback of the doctors.

Steps: Give the app to patients and have them perform the maneuver while under the supervision of a doctor.

Post-Conditions: Have a final, refined algorithm and have confidence in our app.

Test ID: 007

Feature: Survey Link

Purpose: Test if it is possible to bring the link up on the main page before completing the treatment.

Pre-Conditions: Open the app, there shouldn’t be a link on the main page. Steps: Progress through the treatment.

Post-Conditions: Go back to the main page, there should be a link.

Test ID: 008

Feature: Survey Link

Purpose: Make sure that the link directs to a secure form for the patient to fill out

Pre-Conditions: Open the main page of the app with the link on it.

Steps: Click the link.

Post-Conditions: Open to a survey page.

Test ID: 009

Feature: Survey Link

Purpose: Make sure the data comes through in the duke REDcap system.

Pre-Conditions: set up our database to link to the survey.

Steps: Have the user fill out and submit the survey.

Post-Conditions: The information comes through to the REDcap system.

Test ID: 010

Feature: Video Main Screen

Purpose: Make sure that the video plays and is visible in both horizontal and vertical orientation.

Pre-Conditions: Open the app to see the video.

Steps: Click play, and turn the video all different ways.

Post-Conditions: Confirm that the video still plays and is visible.

Test ID: 011

Feature: Video Main Screen

Purpose: Confirm with patients that the video is helpful in their understanding of the movements required.

Pre-Conditions: Get a tester who is not familiar with the process.

Steps: Have a new user watch the video.

Post-Conditions: Ensure that the user has an understanding of the maneuver.