This is the version of BAIS (PeopleSoft) where you will perform the test script/scenario (referred to as “Tests” on this site) assigned to you and do the things you would normally do for your regular work. 

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. If you need additional support, please contact the DoIT Service Desk.

Are you having trouble logging in? Check out the troubleshooting tips.

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.

1. Execute your assigned Tests

   1. • For Financials, test scripts can be found linked from the Business Process / Testing Scenario in the Smartsheet My UAT Test Scenarios report.

      • For HCM, there are no step-by-step scripts and testers should rely on their business knowledge to perform tests based on provided scenarios.

• • • • • Data/transactions in UAT as of: TBD

        • Payrun in UAT: BAIS has processed the weekly payroll TBD and the biweekly payroll TBD ; Users will test in pay period TBD  and TBD  

2. Grab Screenshot Evidence

   1. • 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.

        1. • • 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. 

             • NOTE: We do not expect any change to the way you work. Any unanticipated changes should be reported as defects.

3. Save the Screenshot

   1. • 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. 

4. Update the Test Script in Smartsheet

   1. • Update the Test Script status

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

5. If your test fails, submit a BAIS Defect Form 

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

      • Submit a ticket through the Defect Form. 

      • Be sure to:

        1. • 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. 

It's important that testers understand their roles and responsibilities. Be sure you review the below and ask any questions you have about your role in UAT.

Ensure required testing is completed fully:

• • • Update Smartsheet to ensure the current status of a test is accurately reflected

    • Document evidence for tests performed in the appropriate location and/or confirm that tests performed during the BAIS Internal Testing match your expectations.

    • Submit additional tests performed

    • Log defects for each test script failure

    • Promptly retest defects upon receiving notification

    • Ensure all assigned test scripts are completed

    • Identify any additional testing scenarios if they haven't been previously identified and complete those scenarios. New scenarios can be logged via the New Test Script Submission. 

Ensure required testing is completed on time:

• • • Understand the testing schedule

      • Testing is anticipated to begin Thursday, April 17 and all testing should be completed as soon as possible but no later than 5/9.

    • Stay up to date on any delays

    • Attend testing status meetings as required

    • Monitor the UAT Google Chat

    • Escalate any issues or roadblocks that could impact the testing schedule

    • If you need support, connect with us!