Quality Assurance (B2C)

Quality Assurance is important in identifying issues before they impact your customers and, depending on the nature of your project, there are several different types of quality assurance testing that you’re going to want to consider as part of your integration with Login 3.0. All QA configurations and testing setups involving Login 3.0 must be handled by the UPBOND team upon request:

• Is your application easy to understand and use, even by those with a disability?

• Does your application need to work across various different browsers and devices?

• Does your application need to work in multinational and/or international environments?

• How will your application perform when subjected to unexpected production loads?

• How can you ensure your application is safe from security-related vulnerabilities?

Login 3.0 has already been designed and built following usability and accessibility best practices and provide tested out-of-box support for a whole host of browsers and devices. Support for internationalization (I18N) is also provided out-of-box, with built-in extensibility designed for custom multi-language and localization (L10N) situations.

To ensure functional requirements are met and unexpected events are handled correctly, guidance is provided for testing the integration between your application(s) and Login 3.0, and for unit testing individual extensibility modules.

Integration Testing

It is a recommended best practice that you set up different tenants for development, testing, and production as discussed in Architecture guidance for SDLC support. Login 3.0 allows you to configure variables that are available from within custom extensibility; these can be thought of as environment variables for your Login 3.0 tenant. Rather than hard code references that change when moving code between development, test, and production environments, you can use a variable name that is configured in the tenant and referenced by the custom extensibility code. Tenant-specific variables must be configured by the UPBOND team.

Best Practice

It’s a recommended best practice to use variables to contain tenant-specific values as well as any sensitive secrets that should not be exposed in your custom code. If your custom code is deployed in GitHub, then using a tenant-specific variable avoids exposure of sensitive values via your GitHub repository.

Test Automation

You can automate your overall build process by incorporating deployment automation as well as test automation. This can be used to deploy new versions of configuration and/or custom code to Login 3.0 and execute automated tests. If the tests uncover any failures, the deployment automation capabilities can be used to revert to the last working version. All test automation configurations must be handled by the UPBOND team. For further information, see the deployment automation guidance provided.

Mock Testing

In a balance between Login 3.0’s load testing policy and the desire to load test, it is common practice among Login 3.0’s customers to mock out Login 3.0’s endpoints. This is a valuable practice in order to ensure that your application works with your expected interfaces without having to restrict your testing, and tools such as MockServer, JSON Server, or even Postman can be used to assist. Contact the UPBOND team for support in setting up mock testing environments.