Fast Pass Parking

Test Results

COP4331C Fall 2014

Modification history:

Team Name: Group 13

Team Members:

• Alex Gordon
• Darin Doria
• Ivan Lugo
• Jason Braswell
• Kyle Mera
• Pedro Poveda Quevedo

Objective: User login/sign-up page (All users)

Description : Three types of users (Attendant, Company, ParkingUser) should be able to login using a username and password from the login page of the app. Company and ParkingUser users will be able to sign up for the app from this location.

Conditions : Conditions described in aforementioned general testing conditions. This page requires no previous navigation by the user.

Expected Results : If logged-in successfully with username/password combination, user should be directed to index page of application. If wrong username/password, invalid credentials message should appear. If user is signing up, they should pick whether they are a parker or a company. Users will fill out data needed and then be redirected to appropriate index pages.

Actual Results : When attempting to log in with an unknown user name or password, an error is thrown, and unable to log in. Upon registering, user is able to fill in information and create an account successfully. After registering, user is redirected back to login page. The choice of which kind of user is accessing the app was not done because a decision was made to split the enterprise B2B application from the parking users.This test case was tested on an iPhone 5S and was marked as PASSED.

Objective: User dashboards (All)

Description : All index pages for users should have a dashboard which gives a summary and navigation ability to each of the users features.

Conditions : Conditions described in aforementioned general testing conditions. This page should be accessed shown after login.

Expected Results : User will see dashboard and be able to get to any of the predefined features listed.

Actual Results : Users, upon logging in, were shown a map and parking passes as their dashboard. This test case was tested on an iPhone 5S and was marked as PASSED.

Objective: Parking lot selection (ParkingUser)

Description : Parking users should be able to select a parking lot. By default, the application should see if the user is within the GPS coordinates of a predefined parking lot location. Parking lots should be shown to user in ascending order based on distance.

Conditions : Conditions described in aforementioned general testing conditions. This page should be accessed from index page of this user.

Expected Results : User will see list of parking locations nearest him/herself, along with an accompanying picture. Upon selection user will move to pay for parking screen.

Actual Results : When the user has logged in, s/he is immediately shown a map which will display any parking lots if nearby. The parking lots are shown in a list below, sorted by distance. This test case was test on an iPhone 5S and was marked as PASSED.

Objective: Pay for parking (ParkingUser)

Description : Allows for user to select a time to park until. Shows the rate and total amount.

Conditions : Conditions described in aforementioned general testing conditions. This screen will be accessed from the parking lot selection screen.

Expected Results : User will use a time picker to select a time to park until. The rate of the lot multiplied by the time will show the amount to pay. Once user selects and confirms, payment will process.

Actual Results : After clicking on a parking lot, add time button was hit. A time selector was displayed. After time was selected, a parking pass was created and shown with the expiration date listed. Additionally, funds were removed from the account of the user buying the pass. This test case was tested on an iPhone 5S and was marked as PASSED.

Objective: Parking expiration notifications (ParkingUser)

Description : Notifies parking users that their time is about to expire and allows them to add more time.

Conditions : Conditions described in aforementioned general testing conditions. This screen will be accessed from the pay for parking screen.

Expected Results : Server will automate sending messages to users 15 minutes before expiration. A notification should appear on the users screen (with respect to notification settings on device). Upon selecting the notification, the user will be redirected to the pay for parking screen.

Actual Results : It was determined shortly after Deliverables 1 that this objective was a stretch goal. As such, the testing of it was dependent on its completion by the development team. The feature was not implemented in the version displayed in the presentation, and as such, was not tested.

Objective: Manage profile (All users)

Description : Gives users the ability to update general account information, including online payment methods.

Conditions : Conditions described in aforementioned general testing conditions. This screen can be accessed from all pages once logged in.

Expected Results : User will be able to select profile icon from any page once logged in. Then the user will be redirected to screen where he/she can edit basic account information and online payment. Companies will be able to update parking lots and check select statistics.

Actual Results : Using the hamburger menu (sliding to the left), the Manage Profile link was hit, displaying the users profile settings. From here, the password was changed, the vehicle make/model/year was changed, and the email was changed. The settings were saved, then checked by logging out and back in. This test case was tested on an iPhone 5S and was marked as PASSED.

Objective: View cars in parking lot (Attendant)

Description : Shows user who is parked in parking lots assigned to said user.

Conditions : Conditions described in aforementioned general testing conditions. This screen can be accessed from users index page.

Expected Results : Screen should show parking lots Attendant is assigned to. Upon selecting it user will see all cars parked, with data on how much time is left.

Actual Results : This objective was changed via the B2B enterprise application. Instead, a license plate lookup screen was implemented. Upon entering an invalid license plate (one not registered on the app), an error message was displayed. Upon entering a valid license plate, the time remaining on the parking pass display if it exists, also stating if it has expired. Otherwise, if no parking passes exist, a message stating there that there are no passes displays. This test case was tested on an iPhone 5S and was marked as PASSED.

Objective: Create parking lots (Company)

Description : Gives ability to create geo-locations that are defined parking lots.

Conditions : Conditions described in aforementioned general testing conditions. This screen should be accessed from users index page.

Expected Results : User can map out points on a map (polygons) that creates a parking lot. User can create multiple parking lots. User can set hourly rate for each parking lot.

Actual Results : It was determined shortly after Deliverables 1 that this objective was no longer valid due to the B2B enterprise application. It was determined that parking lots would be added by development as companies signed up with FPP. As such, all parking lots were created manually within the database. Therefore, the only testing that occurred was that parking lots entered appeared in the user application at the correct coordinates. This was tested on an iPhone 5S and it was marked as PASSED.

Objective: Create/assign attendants (Company)

Description : Lets company create Attendant accounts for their company.

Conditions : Conditions described in aforementioned general testing conditions. This screen should be accessed from the users index page.

Expected Results : User can create Attendant accounts and assign accessible parking lots that the user can attend.

Actual Results : It was determined shortly after Deliverables 1 that this objective was no longer valid due to the B2B enterprise application. However, there was no way to programmatically sign in as different Attendants on the B2B application. The ability to log in to the B2B under different companies therefore failed.

Template created by G. Walton (GWalton@mail.ucf.edu) on August 15, 2000.

This page last modified by Jason Braswell (Jason.braswell@knights.ucf.edu) on 11/24/2014.