Go live checklist for Nevada County

[thekaveman]

This task documents a two-phase go live for Nevada County.

Phase 1: Validation testing

This configuration occurs in test.

• Link additional products to sample group
• Create a new TransitProcessor instance with details for the live system
• Ensure the Nevada County nevco-payment-processor-client-secret is updated
• Ensure the Nevada County agency is up to date with this TransitProcessor reference and config data
• Ensure a flow for Older Adult is configured for Nevada County, see group details below
• Confirm that you can successfully go through the flows with sample user and real payment card details

Phase 2: Production

This configuration occurs in test.

• Update the Nevada County nevco-payment-processor-client-secret, go back to the QA value
• Disassociate the live TransitProcessor from the Nevada County agency, go back to the original QA TransitProcessor
• Update the Older Adult flow to remove the sample group ID, go back to group ID from QA 1ad3c030-70b6-4948-b417-40d332c58a96

This configuration occurs in prod.

• Ensure a flow for Older Adult is configured for Nevada County, group details below
• Ensure a flow for Medicare is configured for Nevada County, group details below
• Activate Nevada County

[o-ram]

For testing purposes, a Test Group has been set up in the Littlepay production portal and the "senior" product suite will be associated to the group.

Test Group ID: 1ab565da-a617-4cd0-ac5c-6167540bc274

The following Product IDs below should be associated to it.

Discount Product ID: 09d8bef8-3f44-48ab-8e60-e8a5b1f3d2e2
Discount Time cap ID: f61eb087-5b4e-447f-ba8e-48852e4e826f
Discount Day cap ID: 2ff9ea8c-73c3-4667-bc33-81b8ee1a2bd5
Discount Week cap ID: e485db41-9150-43d7-b573-bc14d4eb0244
Discount Month cap ID: a48d8cdc-460b-4828-acae-478be42f9b9b

Littlepay won't let me associate a newly created group to an already created product for some reason, @angela-tran @thekaveman are you able to make this product<>group association on your end? (example image, the area to edit the group associations is greyed out)

I've pulled all product and group IDs (senior 65+, Medicare, etc) that will be needed for Nevada to go live, but will put those in a different comment so it is clear what is needed for testing.

[thekaveman]

@o-ram thank you!

Are we testing only Older Adult for the production validation? Are the discount products the same for Medicare?

[o-ram]

As of now, we have only planned to test Older Adult for production validation. The discount products for the Medicare group do have different product IDs (so the transaction data can drill down into rider metrics for different discount groups), but they are exactly the same as the Older Adult ones in terms of fare structure/content. So, if the older adult products work, the Medicare ones should as well.

That said, I could push for doing testing for the Medicare group as well if that would be the preference.

Here is the information for the additional (non-test) groups:

Medicare Group ID: d8dccb19-cef5-43ef-a97e-0444a6a7d0015.

• This group ID should already have all of the following product IDs associated to it:

  • Discount Product ID: 9a21a110-6f5e-4799-b6ce-2d7fdfa9f622
  • Time cap ID: 1bd0b18b-620a-41df-92b9-18c625102bcf
  • Day cap ID: 02255f33-ddf0-4ac9-a134-fd527d9acc99
  • Week cap ID: 96de0d17-e408-417b-bd00-cf58102a8bda
  • Month cap ID: a5573ce4-65cc-49b0-9ceb-5b67db8e6673

Older adult group ID: d9a7c51e-bcbd-4a2d-92fe-38267e4926525

• Should already have all the same product IDs associated with it as the test group

Additionally, I do have group information for groups that had been created for people with disabilities and youth, as those were going to be in-person options before the restrictions got put in place. I am continuing to hold on to them because I'm not sure if we can do anything with them right now. Let me know if you'd like me to share those right now as well, hold on to them, discuss further, etc. cc @indexing

[thekaveman]

I'm working on the Phase 1 configuration

[thekaveman]

@o-ram @indexing @angela-tran @machikoyasuda @lalver1

Nevada County is configured for production validation testing of the Older Adult flow at https://test-benefits.calitp.org/nevco.

I ran through it myself and confirmed:

• Test Login.gov credentials work
• Test payment card details do not work
• Real payment card details do work
• My funding source is enrolled in the group

FYI I turned off Medicare while we are doing this production validation testing, since that flow wasn't configured for it.

Marking this as Paused while that process continues. We can mark it as Todo when we are ready for the final production configuration.

[o-ram]

Thank you!! Can you refresh my memory on how the test Login.gov credentials work? Is it the same process as described in this old SacRT doc? Basically, Nevada follows the steps to set up a sandbox account and then enrolls? Or do we provide test data?

[thekaveman]

Thank you!! Can you refresh my memory on how the test Login.gov credentials work? Is it the same process as described in this old SacRT doc? Basically, Nevada follows the steps to set up a sandbox account and then enrolls? Or do we provide test data?

Yes, Nevada staff will need to create their own sandbox Login.gov account. We have more details in the Benefits Testing Data doc

The official Login.gov docs are here: https://developers.login.gov/testing/#testing-identity-proofing

Nevada can use our sample proofing-senior.yml file for an Older Adult. They will upload this file during the step that sandbox Login.gov asks for a photo of their driver's license (use the file for both the front and back photo).

[o-ram]

Thank you @thekaveman! Test instructions have been passed along to Nevada County.

[thekaveman]

Today I responded to a request from Nevada County staff and provided access to our proofing-senior.yml file for creating an eligible Older Adult Login.gov sandbox account.

[o-ram]

A Nevada County staff member successfully created a sandbox account and used it to enroll in Benefits. I can confirm that the test group in the Littlepay production portal now shows 2 cards as being linked to this group.

Testing is planned to take place next week, so I will check in with the agency in early Jan!

[indexing]

I spoke with @o-ram yesterday. Testing is underway, and it revealed some issues, so go-live may be the week of 1/13, but more likely the following week, 1/20.

[o-ram]

Update! Robin is conducting the final test scenarios over the end of this week and start of next week. There is also some troubleshooting going on with the vendors regarding location info accuracy.

Good news: the discounted products worked as expected, and there are no issues on that side of things.

Launch? Looking at a tentative public launch date of the first week of Feb. Things might all be live before then, but would be kept very quiet if so. So, I think we have the ability to push to production this month as long as there is no press/comms/attention from our side.

[indexing]

@o-ram I propose we do exactly as you discuss here: a soft launch. Let's configure and launch Nevada County to production as soon as you give us the thumbs up. They can they promote when they are ready.

We'll move when you give us the word.