FSPT User Acceptance Testing

1. Student PIDs: Testers should be prepared with at least 10-20 student PID numbers from their own department.

2. Funding information: Testers should be prepared with at least 5 PTF (project, task, funding source) combinations.

   1. Need to work backwards from an AIDID you used in AY2324? Use the same OFC : ISIS : ProSAM Funding Code Map (Graduate FSU) Google Sheet to do a “reverse lookup”.

   2. Alternatively, double check with your fund manager or fiscal contact - they may have new funding strings that you can use for tests!

3. Scenarios: Testers should be prepared to recreate scenarios that have happened in real life. We’re looking to confirm that FSPT can handle single transactions, retroactive changes, funding changes, multi-month stipends, and more!

FSU will provide test scripts to help you document your test scenarios and report back to us the results. The scripts are an outline to follow, however, we will ask testers to recreate real-world scenarios from their own work experience in the new FSPT - the more complex the better!

Find general information on test scripts below: https://ucsdcollab.atlassian.net/wiki/spaces/GDCP/pages/894304796/FSPT+User+Acceptance+Testing#Where-to-find-test-scripts-%26-how-to-make-your-own-copy%3A

Find specifics for each week of testing below: https://ucsdcollab.atlassian.net/wiki/spaces/GDCP/pages/894304796/FSPT+User+Acceptance+Testing#Weekly-Testing-Information-%26-Notes

Review the FSPT project timeline and milestones here.

User acceptance testing (UAT) for FSPT Stipends is expected to run asynchronously through at least the end of August 2025. Testing may continue into September - this will depend on the test results and the nature of any bugs found during testing.

Weekly check-in cadence:

Monday: all users, debrief prior week’s bug and development notes
Wednesday: FSU & BFS teams only (back-end processes)
Friday: end users, review system-generated outcomes

You can learn more about the entire project by visiting the ESR website or the Campus Partners Financial Support Request Tool (FSPT) collab space.

Please also see FSPT Stipends Two-Pager: Call for Testers for an overview and testing participation FAQs.

In addition to the specific user tests, we need your help to write the FSPT User Manual!

Please use comments, action items and emoji reactions within the DRAFT: FSPT Manual document so that the FSPT team can track changes as bug fixes are deployed and new functionality .

Note: this document is intended to be for all users (including those in FSU and other central offices); please suggest edits with that in mind. To prepare for training and hypercare, the FSU and OCM teams will use this as the source document for creating training videos, knowledge base articles (KBAs), and other reference materials.

We want to hear from you!

For feedback on the testing process, please use this ⁠FSPT Tester Feedback Form Google Form.

To submit an enhancement request (a change to the FSPT system), please complete the FSPT Enhancement Request Form, which will open a service ticket.

A test script for each week of testing will be saved on Google Drive.

Both the folder and the sheet will be named with the start date of each week (e.g. the folder ‘FSPT UAT 2025/08/11’ or the sheet ‘FSPT UAT 2025/08/11 Template’).

To access the test script, navigate to the UAT-FSPT folder below; then, click in to the relevant week’s folder. Next, navigate to the relevant week’s test script (sheet), and make a copy for yourself (instructions on how to do this are found below).

Access to the FSPT UAT Google Drive folders and documents is provisioned via Google Group. Testers who have completed the sign-up process are included in the membership of the Google Group.

Haven’t signed up as a tester?

• Do so here: FSPT Stipends: Testing Sign UpPreview

Signed up as a tester, but still can’t get in?

1. Make sure you see your @ucsd.edu AD account here: Group Membership fspt-uat-g

2. If you do see your email address, double check you are signed into the corresponding Google account - if you are having trouble, see Clear cache & cookies or Can't sign in to your Google Account

3. If you do not see your @ucsd.edu address send a message on the FSPT UAT MS Teams Channel (note: this channel is also restricted to testers who have completed the sign-up form)

See: Make a copy of a file

1. Save your copy in the same folder as the template for this week’s testing

2. Name your copy with the same prefix, and your last name (e.g. ‘FSPT UAT 2025/08/11 Swiderski’)
   
   

   Open

   

3. Change the sharing permissions on the file to “Anyone at UC San Diego can Edit”:
   
   

   Open

   

    

   Open

   
   Open

   

Please save your copy of this week’s test script in the same folder as the template (for each week of testing). This helps keep the FSPT project team coordinated in reviewing test results and comments, so that we can more quickly find, replicate, and address bugs.

Yes, and: it’s important that you record the steps you took and the expected vs. actual outcome. The FSPT project team needs this information in order to replicate and address any bugs or other comments.

If you’d like to test something that isn’t in the formal test script, simply add a row to the bottom of your test script, and record the steps you took plus any pertinent details (PID, amount, dates, PTF, what you expected, if it worked as you anticipated - and if not, why the result is a problem).

Yes, and: it’s most helpful if you save those images in your test workbook for the week (ideally near the row of the test – but we know spreadsheets are imperfect, so please do your best!).

Yes! Other testers may have run into the same error or have the same question - it may be useful to find out if it is a bug (and how widespread it is), or, if it is an operator error (it happens to all of us! ). Users may also provide peer support to each other, just as in the course of normal business.

If you find a bug, even if it is discussed on MSTeams, please record the error in your testing sheet. This is important documentation for the project team and will be used for reviewing, replicating and fixing bugs.

Yes! Leave comments on the

For feedback on the testing process or to submit system enhancements, see “Testing Feedback” under the https://ucsdcollab.atlassian.net/wiki/spaces/GDCP/pages/894304796/FSPT+User+Acceptance+Testing#Resources-%26-what-to-expect-during-testing%3A section above.

Monday, August 18

• Please pay special attention to the FSPT Manual this week for tests 2-4. We are looking for feedback - please think about the manual from the POV of a brand new graduate coordinator, or even training another colleague to use the system should you be out on vacation

• There are a couple of known bugs - you will find reference to these in Column F of the test script for this week (“FSPT Team Comments”).

Monday, August 11

Updates from the week:

• CCOA fields were (mostly) removed from the stipends tab and download - making files easier to read and use, yay! (There are a couple more fields still present, and a requirement for paymentType that will be removed shortly. We expect these to be resolved sometime in the following week!).

• Thank you to our testers for feedback on the Download and Upload Functionality section of the FSPT Manual this week!