You can access the test scripts assigned to you via the Smartsheet My UAT Test Scenarios report.

• When logging into Smartsheet, remember to click the Sign in with Google option and log in using your City of Boston credentials.

• If you have trouble accessing Smartsheet, please email baismod@boston.gov for support.

There are also pillar specific reports:

• All HCM Test Scripts

• All FN Test Scripts

To access environments from your office location:

Use one of the following links. You will need to sign in with your username and password.  

FN URL: https://psfnuat.bais.boston.gov/

HCM URL:  https://pshruat.bais.boston.gov

It is recommended to test on-site to avoid any VPN/RDP issues. However, if you need to access environments remotely:

You must first log into VPN or on to your work computer remotely and then use the above links.

If you need assistance with installing or using VPN/RDP, please review these instructions and, if you need additional support, please contact the DoIT Service Desk.

If you're trying to access the HCM UAT environment or FN UAT environment and having trouble, here are some helpful troubleshooting tips.

If you click on the link to the UAT environment and cannot get to the PeopleSoft log-in page:

• • Review "How do I access the test environment?" above to ensure you are accessing them correctly.

  • If you have questions or need assistance, please email BAIS@boston.gov.

If you are able to get to the log-in page but aren't able to log-in:

• • Ensure you’re in the correct environment. 

    • • If you're testing Financials, you should be in the FN UAT Environment.

      • If you're testing HCM, you should be in the HCM UAT Environment.

      • Check to make sure you see the letters “uat” in the URL (psfnuat.bais.boston.gov or pshruat.bais.boston.gov).

  • Use your 6-digit employee ID and your Test environment password to log in.

    • • If you don’t remember your password you can use the reset password link on the sign-in page to reset it. 

      • If you have questions or are still unable to log in please email BAIS@boston.gov.

  • Some users have reported that logging into the PeopleSoft UAT environment appears to "spin" or they get a notice that the page has been redirected too many times. 

    • • This can happen if you use the UAT environment in the same browser (e.g. Google Chrome) that you use to access the Production PeopleSoft environment and is a result of the way that data is cached (stored) on your browser for PeopleSoft.

      • This is not an issue with your browser or PeopleSoft and will not be an issue in Production.

      • We recommend the following:

        • • Using the Incognito mode in Google Chrome to access the UAT environments

            • • To open an incognito window in Google Chrome hit Ctrl+Shift+N. You can visit Google Help for more details. 

              • If you've already been using Incognito mode and you've been experiencing difficulties logging in, try closing your Incognito window and opening a new one.

          • Using a different browser than you typically use (such as Microsoft Edge or Firefox) to access the UAT environments

          • Clearing your cache and then accessing the UAT environments

            • • To clear your cache in Chrome hit Ctrl+H to open the History Page and select Clear Browsing Data from the menu on the left.
                We recommend selecting “All Time” from the time range dropdown options and checking the first three boxes. You can visit the Google help page for more details. Whenever you access multiple PeopleSoft environments using the same browser, you'll need to clear your cache each time.

              • To clear your browser cache and cookies in Microsoft Edge, go to Settings > Privacy > Clear browsing data, select Choose What to Clear, select Cookies and other site data, and Cashed images and files, then click Clear Now.

UAT will tentatively begin Monday, April 14 and end on Friday, May 9. See the calendar for details.

HCM UAT:

• • Data/transactions in UAT will be up to date as of: March 28, 2025

  • BAIS has processed the biweekly payroll 2025-13 and the weekly payroll 2025-14

  • Users will test in pay period 2025-15 and 2025-16  

    • Please prioritize tests that depend on these payrolls

  • In the event of defect resolutions requiring an additional pay period we will run as needed

  • We will communicate payroll processing details via Google Chat

• No, historical reports will not appear in the UAT environment. 

• Only reports that are newly generated as a part of the UAT process will appear. 

• Rest assured, all historical reports will appear in Production as normal.

In the UAT environment, e-mail addresses are masked to a default email address (mis.hcmworkflowtest@cityofboston.gov) to avoid sending emails from the test environment.  See a walkthrough of this process here.

For the FN UAT environment:

• • • Please email baisfnsecurity@boston.gov to have your e-mail address changed

For the HCM environment:

• If your testing requires that you receive email notifications, please navigate to:

  • Main Menu > Self Service > Personal Information > Email Addresses

• Once you are there:

  • Change the Home email to your Boston.gov address 

    • If you don’t have one, click Add Email Address

  • Check Preferred and click Save before exiting the screen.

 For BOTH environments:

• • • If you need e-mail addresses changed for someone else or an external user, please chat with us in the UAT - HCM or UAT - FN chats or contact us at baismod@boston.gov.

3. If you run into any difficulties with resetting your password, please chat with us in the UAT - HCM or UAT - FN chats or contact us at baismod@boston.gov.

How much time UAT will take depends on how many different tasks you do in PeopleSoft in your work and how many scenarios you need to run through to feel comfortable that the upgrade has gone successfully. It also depends on how you choose to share the tasks, that is, whether you choose to complete your scenarios yourself or delegate them to another member of your team. 

Reach out to the BA who works on the module(s) in question using the Google Space if you have particular questions about a given scenario. BAs will be involved in helping you gather data and resolve issues. 

You will be able to test on all browsers like Chrome, Edge, and Safari.

You will be using your employee ID and the password you have for the Test environment. 

• • • There is a reset password link on the log-in page if you have forgotten your password. 

    • Please email BAISmod@boston.gov if you feel you don't have the access you need in order to complete your testing. 

There are four basic steps to collect and save test evidence:
See a walkthrough of how to do this here.

1. Grab Screenshot Evidence 

2. Save it on your computer, you can put it in a document or just save the image

3. Attach the screenshot to the test script in Smartsheet using the "paperclip" icon 

4. Update the test script status

   • • If your test fails, submit a request via the BAIS Request Form. Be sure to select "Testing: PUM Update UAT Issue" and also attach the screenshot.

1. Grab Screenshot Evidence

• • • Use your preferred screenshot tool to take a screenshot of the evidence.
      Learn more about how to take a screenshot and upload it to the Smartsheet My UAT Test Scenarios Report.

      • • If your test is passing, screenshot the successful results of your test, such as the results of a query, process, or transaction,  that show that you were able to successfully run your business transaction. 

        • If your test is failing, screenshot the part of your test that fails, along with any relevant error messages or issues observed. 

2. Save the Screenshot

• • • Save your screenshot either as an image or the word processor of your choice (Google Docs or MS Word). Feel free to add notes or highlights to your image, if you feel it will be helpful. 

3. Update the Test Script in Smartsheet

• Update the Test Script status

• Attach the screenshot file to the test script in Smartsheet using the "paperclip" icon.

4. If your test fails, submit a BAIS request 

• Copy and paste the error message that you observed if you saw one.

• Submit a ticket through the Defect Form. Be sure to:

  • • Attach screenshots of the defect;

    • Enter the Test Script Number;

    • Write down the exact steps you took to get to the error;

    • Provide as much information as possible about the defect. 

Defects will be logged using the Defect Form. This will begin a triage process managed through a workflow in Smartsheet.

• Screenshot the results of your test.

• Copy and paste the error message that you observed if you saw one.

• Submit a ticket through the Defect Form. Be sure to:

  • • Attach screenshots of the defect;

    • Enter the Test Script Number;

    • Write down the exact steps you took to get to the error;

    • Provide as much information as possible about the defect. 

• After you've logged your defect, you will receive a confirmation e-mail from Smartsheet that contains a request number. Please copy this number and put it in the 'BAIS Request #' column in the Smartsheet My Test Scenarios report.

If you have questions about this process or need assistance, please email BAISmod@boston.gov. 

• When a defect is logged using the Defect Form, this will begin a triage process managed through a workflow in Smartsheet.

• Once the defect has been addressed, you will be notified that the test scenario is ready for retesting.

• Once you run the retest, you will indicate in My Test Scenarios the outcome of your retest in the "Test Script Status" Column.

  • • Pass - Independently Tested in UAT

• Smartsheet My Test Scenarios

• Defect Form

If you have questions about this process or need assistance, please email BAISmod@boston.gov. 

Below are the statuses for reporting on Smartsheet.

• • • Not Started: Testing has not started for this test script

    • In Progress: Test script execution is in progress (typically used for longer running tests)

    • Pass - Verified BAIS Test Results: The tester has reviewed the results from the BAIS test team and determined that the test results from BAIS appear to their expectation and they will not perform any additional testing. 

    • Pass - Independently Tested in UAT: The tester completed the testing independently, in addition to the testing performed by BAIS. Testing was completed, the tester states that it worked as expected and has attached evidence of their testing. 

    • Fail: If the test results do not meet the test requirements

    • Temporarily On Hold*: The execution of the test script is on hold until later in the test cycle (for example: waiting on an integration to be ready to test, or waiting on contact with a third party)

    • Canceled*: The test will not be tested. Some reasons this might be applicable include: the test is no longer a valid business process, the test script is a duplicate script, or the tester/department has decided to deprioritize testing this script. Canceled test scripts require a reason in the Reason for Cancellation column. 

    • Delete - No longer applicable: This test script is no longer needed and should be removed from the UAT test script library

*Note: Any canceled or on hold tests must be justified, e.g., duplicate script, script not applicable to business process, functionality not ready at the planned time of execution, etc.

• New test scripts can be logged using the New UAT Scenario form. Fill out the form to the best of your ability with any scenario you feel isn't currently covered by existing scenarios.

• When you log a scenario, a member of the BAIS team will review your scenario and add it to the UAT list of scenarios as appropriate.

• If you have questions about this process or need assistance, please email BAISmod@boston.gov. 

Learn more about the terms and acronyms used here.