Release #5 Extra Features | Included Features Full User Documentation - cseseniordesign/reservations GitHub Wiki
Features to be Included in Release #5
Story #128 Update New Member Signup
Dev Testing Instructions
Make sure you are on the most recent version of the dev-update-new-member-signup branch.
Navigate to /new_members/ and sign up for a new member orientation.
Fill out the form and make sure that all fields that are required must be filled out.
Verify that a UNL Student/Staff/Faculty with Garage or Lot parking but without perimeter parking must check the box asking them to request parking at NIS from UNLPTS.
Submit the form.
Verify that there is a user created who has the same information as was put on the new member signup form.
Log in with development2 so that you have permissions to view the Admin -> Users page.
Navigate to the Admin -> Users page and search for the new member you just created or any of the development accounts.
Edit the user and ensure that you can now access the user's vehicle and emergency contact information from the edit user page.
Ensure that all create, update, and delete functions work for the vehicle and emergency contact information. Ensure that an emergency contact is only saved if a name, relationship, and primary phone are provided. To delete you would just clear out all of the fields for the emergency contact and save.
Navigate to the My Account page and ensure that you can now view your account's emergency contact information.
Ensure that all create, update and delete functions work for the emergency contact information. To delete you would just clear out all of the fields for the emergency contact and save. Ensure that an emergency contact is only saved if a name, relationship, and primary phone are provided.
Ensure there are no errors in the console throughout your testing and that the page is still responsive on all screen sizes.
Follow steps 3 and up from the dev testing instructions above.
Story #138, #139 Track Broken Equipment
Dev Testing Instructions
If on a dev (local host) environment (i.e. not staging or production), make sure you are using the UNL VPN. This is necessary for emails to send properly. NOTE: several IP addresses have been blocked from sending emails. As of this page’s creation, the “US South” server works for me. However, it is entirely possible that none of the VPN servers will allow the sending of emails. In this case, testing must occur on the staging/production environment.
Ensure you are on the most recent version of the dev-track-broken-equipment-and-notify-impacted-members branch.
Start your dev environment and log in with the account associated with your email address.
Ensure you have the required permissions:
Go to Admin > Users.
Find yourself and click Edit.
Make sure all the boxes under Manager Permissions and Make Super User are checked. Click Update.
Navigate to the Reserve Equipment tab.
Find a tool you wish to reserve but do not reserve it yet.
In a new tab, navigate to Admin > Tools.
Ensure the tool you wish to reserve does not have its corresponding INOP box checked. If it does, uncheck it and click the Update Tools INOP Statuses box at the bottom of the page.
Go back to the Reserve Equipment tab you previously opened and reserve the tool for any date in the future.
Go back to Admin > Tools and check the INOP box for the tool you reserved. Click the Update Tools INOP Statuses box at the bottom of the page.
You should receive an email at the address you have listed on your My Account page.
Verify the event is no longer listed under My Reservations on your Manage Your Studio (home) page.
Navigate to the Events tab under Admin.
Click New Event from Preset
Verify the tool you marked as INOP is not displayed in the reservable tools boxes.
Navigate to the Reserve Equipment tab.
Find the tool that you marked as INOP and try to reserve the tool. A message should be displayed telling you the tool is “Currently unavailable due to service.”
Log in as an admin user, then follow steps 4-17 from the dev testing instructions above.
Story #147 Add Announcements
Dev Testing Instructions
Ensure you are on the most recent version of the dev-announcements branch.
Start your dev environment and log in with development2 so you have all permissions.
Navigate to the Admin -> Announcements page
Ensure that if there is an active announcement that the announcements textbox is prepopulated with the announcement. If not, write an announcement and save it. The announcement should now show on the home page.
Go back to the Admin -> Announcements page and delete the announcement. The announcement should no longer show on the home page.
Ensure there are no errors in the console throughout your testing and that the page is responsive on all screen sizes.
Login with a test account that has an active membership.
Select a reason for visit along with a studio space from the list then press the check in button.
Make note of the time and options selected for later.
Login with a test account that has an inactive membership.
Repeat step 4
Navigate to http://0.0.0.0:9393/login/ or again your environments equivalent and login with an admin account.
Click on the admin tab and select Check In Log from the list of options.
Check In Log should also be an option when hovering over the admin selection.
On the page verify that the chart showing numbers of visits to the various studio spaces aligns with what you chose when checking in on the two test accounts.
Scroll down and see if your 2 check ins appear below the search options with the correct values.
Attempt to search by the various parameters to single out one or the other check in instance.
If there are previous instances that exist you can also attempt to search for them.
Scroll back up and click the Manage Studio Spaces button.
Create a new studio space on this page.
Return back to the Check In Log page and see if the newly created space appears along with the others.
At this point you can also attempt to check in again while selecting this new space as an option.
Navigate back to the Manage Studio Spaces page and delete the new space.
Return back to the Check In Log page and see if the space has been removed from all the options.
Note that any check ins that happened under that space will still have that space listed on the log.