Getting started with manual testing

Manual testing is an important part of the feature release and refactoring processes. This testing can take on different forms and is performed in different environments for given scenarios (see When to test below).

In order to test a complete enrollment flow in the app in any environment but production, you will need to use appropriate test credentials for the flow and associated identity provider(s) (IdPs).

The Benefits Test Data document has more information about the supported systems and test credentials for each.

Login.gov

See the tutorial on Using the Login.gov sandbox to learn how to setup a Login.gov sandbox account for testing. Note you can create multiple Login.gov sandbox accounts for testing different scenarios (Older Adult and U.S. Veteran for example).

Agency cards

To test the agency card enrollment pathways, we primarily use sample credentials specific to the Transit Agency:

• Agency Cards (CST)
• Courtesy Cards (MST)
• Reduced Fare Mobility ID (SBMTD)

Payment cards

To test the Littlepay or Switchio card enrollment flows, use sample Payment card information, along with any fake name, any CVV and an expiration date in the future.

Benefits Administrator

To test the Benefits Administrator from the perspective of a Transit Agency user, sign in using the sample Benefits Admin account.

When to test

The following table outlines some key conditions in which different manual testing scenarios should be run.

Condition	Scenario(s)	Environment(s)
New feature development, new UI elements	keyboard, qa	local, dev
Bug fixes, refactors - maintaining existing functionality	qa	local, dev
New or refactored designs, layouts, fonts, colors	keyboard	local, dev, test
New translations and/or updated copy	translations	local, test
New agency onboarding	qa, smoke testing	test, prod
Deployment to test	qa	test
Release to prod	smoke testing	prod