Typical Test Scenarios — FrankieOne

A Test Persona is a pre-configured individual or business profile available in our sandbox environment for testing purposes.

Basic Testing Scenarios

Successful Match Testing

To verify a successful match:

Select a Test Persona from the test data spreadsheet
Enter the information exactly as shown in the spreadsheet
The required information depends on your Recipe configuration

A Recipe defines the set of verification checks applied to a customer’s profile. See Entity Profiles/Recipes for available configurations.

Failed Match Testing

To simulate a failed match:

Select a Test Persona
Modify one or more values from their original data

1 // Example: Modifying first name
2 originalName: "Bobby"
3 modifiedName: "Bobble" // This will cause a match failure

Avoid modifying the Family Name field as it’s used as a primary key for Test Personas and may cause unexpected behavior.

Dynamic Persona Testing

Dynamic Test Personas

Unlike static Test Data, Dynamic Personas allow you to simulate outcomes with custom information.

Always Match

Always Fail

Force Successful Matches

Use any of these methods to ensure a successful match:

1 middleName: "passall"  // Forces all checks to pass
2 middleName: "onepass"  // Forces one data source to pass

Special Test Scenarios

Specialized Testing Cases

Non-ID Check Failures

Set otherName: "FailNonID" to pass document checks but fail other verifications.

Ensure document-related details (name, DoB, ID) match the Test Data exactly.

Credit Header Failures

To simulate provider-specific failures:

1 streetName: "77 Equifax Street"   // Equifax failure
2 streetName: "123 Experian Street" // Experian failure

PEP, Fraud, and Sanctions Testing

Select a Test Persona marked with PEP, Sanctions, or Fraud flags
Ensure your Recipe includes PEP checks
Execute the verification process

PEP/Sanctions matches are pre-configured and static. Use Test Personas marked as SKIP to bypass these checks and test with external services instead.

1	// Example: Modifying first name
2	originalName: "Bobby"
3	modifiedName: "Bobble" // This will cause a match failure

1	middleName: "passall" // Forces all checks to pass
2	middleName: "onepass" // Forces one data source to pass

1	streetName: "77 Equifax Street" // Equifax failure
2	streetName: "123 Experian Street" // Experian failure