Ensure you are on the most recent version of the dev-add-preset-reservations-and-complete-attendance-checkbox branch.
Start your dev environment and log in with development2 so you have all permissions.
After login in with an admin account, navigate to the Events tab under Admin.
From the toolbox, click the Event Presets button, then create a new preset by clicking the "+ new preset" button.
Select both from the tool authorization and reservation lists and save the new preset.
Edit the created preset by changing both tool authorization and reservation lists.
Navigate to the Events page and create a new event from the newly created preset.
Ensure that all reservation/authorization tools included in the preset are chosen by default on the new event page. Confirm that the checkbox next to tool reservation/authorization is checked to preserve the selected list.
Click on the event title to check the selected tools are saved.
Login from another account and sign up for the newly created event.
Login back to the admin account and navigate to the Events tab under Admin.
Access the event signups list from the signups column.
Take attendance on this page and save it. All tool permissions gained from this event will be deleted when unchecking a checked checkbox.
Ensure that the attended member gets all tool permissions of all authorization tools selected in that event without interfering with pre-existing tool permissions.
Log in as an admin user, then Follow steps 3-7 from the dev testing instructions above.
Story #107 Multiple levels of email opt out
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. It is entirely likely that none of the VPN servers will be able to send email. In this case, testing must occur on the staging/production environment.
Navigate to Admin > Users.
Find yourself and click Edit.
Under “Email Preferences,” make sure both the General and Promotional boxes are checked.
Click Update.
Navigate to Admin > Email.
Click Compose.
Select yourself as the only recipient. You can do this by selecting yourself under the Specific User(s) section.
Optional: select one of the preset emails so you don’t have to type anything later.
Click the Select the Email Type: dropdown menu and select Promotional.
Ensure there is text in both the Subject and Body fields.
Double check you are the only selected recipient.
Click Send.
You should have received the email at the address you have listed on your My Account page.
Click the My Account button in the top right corner.
Check the box I no longer want to receive promotional emails from Nebraska Innovation Studio. so you can test the opt-out functionality.
Click Save.
Repeat steps 2-13.
Ensure you did not receive the email. NOTE: you may receive an alert on the page that says "No Users Selected - This email was not sent to any users." This is the desired functionality as it means all the selected users have opted out.
Repeat steps 6-9.
Click the Select the Email Type: dropdown menu and select General.
Repeat steps 11-14.
You should have received the email at the address you have listed on your My Account page.
Navigate to Admin > Users.
Find yourself and click Edit.
Under “Email Preferences,” uncheck the General box.
Check/uncheck the Promotional box.
Click Update.
Make sure the changes are reflected on your My Account page.
Now we will make sure you do not receive General emails after opting out. Repeat steps 6-9.
Click the Select the Email Type: dropdown menu and select General.
Repeat steps 11-13.
Ensure you did not receive the email. NOTE: you may receive an alert on the page that says "No Users Selected - This email was not sent to any users." This is the desired functionality as it means all the selected users have opted out.
Log in as an admin user, then Follow steps 2-22 from the dev testing instructions above.
Story #106 Update event signup to support signup using code
Dev Testing Instructions
Make sure you are on the most recent version of the dev-add-code-to-event branch.
Start your dev environment and log in with development2 so you have all permissions.
Navigate to the Admin -> Events page
Create a new event from a preset. Ensure that there is now an input field to enter a code. Enter a code, set the event to a time later today, then save it.
Create another new event and set it for another time later today but don't give it a code.
Go to Manage Your Studio -> Trainings.
Sign up for the event without the code and ensure it just signs you up without asking for a code.
Sign up for the event with the code and ensure it prompts you to enter a code. If you enter the wrong code it should not let you sign up.
Go to Manage Your Studio and remove yourself from the signup lists for the event. Repeat step 6 on the Manage Your Studio -> Event Calendar page.
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 #65 Tabs for sorting by workshop area
Dev Testing Instructions
Make sure you are on the most recent version of the dev-sort-by-workshop-area branch.
Start your dev environment and click on the "Reserve Equipment" tab.
Click the "Workshop Category" dropdown menu and choose a category. Click "Search."
You should only see tools with the matching category. Verify that the items shown are the same as the ones you saw before applying the filter. You should not have access to any more tools than you had before you applied the filter (i.e. tools you are not authorized on).
Navigate to Admin > Events.
Click the "Event Type" dropdown menu and choose a type. Click "Search." Verify that the events listed match the category you selected. If there are no upcoming events, you can create one. Note that you will not see any events if there are no upcoming events with the same type. You can check an event's type by editing the event and seeing what is listed under "Type."
Click the "Past" tab button located above "Upcoming Event Items."
Select any event type from the dropdown menu. Click "Search."
Verify that the event type you selected is preserved when navigating between pages using the pagination buttons under the events table.
Navigate to Admin > Agenda.
Use the "Go to another date" selection and select a different date. Click "Search."
Verify the date format is still displayed correctly (MM/DD/YYYY).
Click the "Workshop Category" dropdown and select a category. Click "Search."
Verify the correct tool reservations are listed.
Change both the date and workshop category. Click "Search." Verify that both fields are preserved.
Story #113 Send email when vehicle information or membership status changes
Dev Testing Instructions
Make sure you are on the most recent version of the dev-add-vehicle-emails branch (since the dev emails are not working perform this testing on the staging environment).
Log in with development2 so you have all permissions.
Navigate to the Admin -> Users page
Search for the user with the first name "Email". You should find a user named "Email Tester". Change the email of this user to your email.
Find the development user with your huskers email and set the expiration date to null and save. After that set the expiration date to an active date. You should get an activation email with steps for getting started and an attached parking map. If you have any vehicles added to your account you should also get a vehicle information email. The Email Tester user should also get this email.
Ensure that whenever you change your vehicle information in the My Account page that you also get a vehicle information email.
Change your development account's expiration date to expire tomorrow. Tomorrow at noon the Email Tester user should get an email saying that your user is expiring and that their parking information will need to be removed from passport parking.
Ensure there are no errors in the console throughout your testing and that the page is responsive on all screen sizes.
Story #104 Create new event type "Scheduling"
Dev Testing Instructions
Make sure you are on the most recent version of the dev-new-event-scheduling branch.
Start your dev environment.
Log in to a super user account.
Navigate to the new event page and check the box to create a private event.
Verify that the event appears correctly on the events table and on the calendar.
Log out of the super user account.
Log into a non-super user account.
Verify that the event does not appear on the events table or on the calendar.
Follow steps 3 and up from the dev testing instructions above.
Story #98 Highlight expired members on agenda
Dev Testing Instructions
Make sure you are on the most recent version of the dev-highlight-expired-members-on-agenda branch.
Have access to two separate accounts one expired and one still active.
ensure at least one of these accounts is an admin account with access to the daily agenda.
On both accounts sign up for an event for the current day.
Check the agenda on the admin account.
The expired accounts name should appear in red text where the active one will appear as normal.
Story #101 Add preset emails
Dev Testing Instructions
Make sure you are on the most recent version of the dev-email-presets branch.
Start your dev environment and log in with development2 so you have all permissions.
Navigate to the Admin -> Email page
Click the manage email presets button to navigate to the email presets page.
On the Manage Preset Emails page make sure there is a button to create a new preset and that there is a table showing the current presets.
Click "new preset" and try to create a preset without filling out all of the required fields. Ensure that an error is flashed and that the preset is not created.
Create a valid preset and ensure that you are redirected to the previous page and that you now see the preset in the table.
Edit the preset you just created and make sure the page loads pre-populated with all the information that you set when you created it. Edit the preset and make sure it updates. If you clear out the required fields and try to save you should get an error.
Ensure that you can delete the preset. Make sure that when you delete the preset it is removed from the database.
Go to compose an email and ensure there is a dropdown at the bottom of the page to select a preset email. Ensure that when you select a preset that the subject and body autofill based on the preset's information.
Ensure there are no errors in the console throughout your testing and that the page is responsive on all screen sizes.