Thank you for participating in the last round of User Acceptance Testing before Fibi go-live!
Please use the reporting form below to share your results. Also use this form if you see noteworthy behavior not associated with a specific script. Every piece of information helps us to detect bugs, or potential enhancements for subsequent releases.
TESTING SESSION SCHEDULE: JUNE 5 – JUNE 15
June 5 & 12: PD Day: Please create lots of different PDs – pointers are on the script files for the day, along with a general feedback form to report findings.
June 6 & 13: Load Test Day: Please log into Fibi at 2:00 pm. Access the system at any other time, but we need lots of people logging in at 2:00 to test performance. Scripts will include lots of copying and other things that load the system.
June 7 & 14: Service Request Day: Reference materials are provided at the script link describing creating, routing and approving Service Requests. The goal of the day is to create and submit different Service Request types.
June 8 & 15: Dashboard & Reporting Day: Scripts will describe adjusting the dashboard and testing report generation and creating custom reports.
June 9: Research Administrators Day: Session is for RAs only. Scripts will describe RA functions. All users my log in at any time, but this 10:30am session is for RAs only.
HELPFUL HINTS:
- Taking a few minutes to create your own PD with an identifying title may help you keep track of your testing.
- If you’re testing validations, it may be easier to copy an existing PD that has been submitted – then you need only do a bit of data entry prior to validating/submitting.
Steps To Test and Report Your Results:
- Go to the test scripts.
- Choose a script, open the excel file.
- DOWNLOAD YOUR OWN COPY.
- Make notations on your copy of the form.
- Save the form to your desktop.
- Complete the UAT online form below.
- Upload your copy of the script file.
- Submit.
UAT FAQs are found in the accordion below this form.
Please remember that Fibi is not “fully baked.” Until we announce UAT is underway, some things may not work…
Log into the testing instance of Fibi HERE. Use your JHED ID (not email address) and polus123 as the password to log in.
You can ask a question by emailing oris@jhu.edu, or from within Fibi at the ORIS Support Link in the upper menu list.
Check the ORIS calendar for any updates or changes.
Group Session Schedule:
- June 5: PD Day: Please create lots of different PDs – pointers are on the script files for the day, along with a general feedback form to report findings.
- June 6: Load Test Day: Please log into Fibi at 2:00 pm. Access the system at any other time, but we need lots of people logging in at 2:00 to test performance. Scripts will include lots of copying and other things that load the system.
- June 7: Service Request Day: Scripts will describe creating, routing and approving Service Requests.
- June 8: Dashboard & Reporting Day: Scripts will describe adjusting the dashboard and testing report generation and creating custom reports.
- June 9: Research Administrators Day: Session is for RAs only. Scripts will describe RA functions. All users my log in at any time, but this 2:00 session is for RAs only.
No. These links and Fibi are available to you 24-7. It can be both fun and helpful to test things in a group, and ORIS will be there to answer questions in person during group sessions.
A script is a spreadsheet laying out exact steps to take to perform a certain function (like adding a Key Person) and the expected result for each step. Each testing task (function) has its own script. Find the scripts at this LINK.
Not really, although the testing scripts are helpful in two ways:
1. They help new users learn and follow the correct way to enter data in Fibi.
2. They standardize the approach to using Fibi to help identify steps leading to any specific bugs or use issues that arise.
That said, it’s also helpful to go “off-script.” As part of your testing, we want you to use Fibi in a free way that might mimic use in the real-world. This is the way to find odd bugs that crop up when a typical “order of operations” is not followed.
However you test, please use the form above to record your results.
