The testing process includes the following steps:
Plan - Review the overall test strategy, develop the test plan, and perform needed analysis for baseline metrics. Identify key business scenarios that are in and out of scope. Document the requirements, if that step has not already been completed.
Prepare - Set up needed environments for performance testing, user acceptance testing, and so on. Review data that is received for migration, before and after the migration testing. Validate high-level system requirements, and then develop needed scripts.
Execute - Run test scripts, analyze results, identify potential bottlenecks, and then review failures and behaviors.
Report - Prepare a detailed assessment of the reporting plan, results, and plan of action
The solution architect should be part of the discussion regarding the amount and type of testing that is required for a project.
Common types of tests in Microsoft Power Platform include:
Unit tests - Performed by the app builder, business analyst, functional consultant, or developer.
Functional tests - Verify that the implementation meets requirements.
Acceptance tests - Performed by users to give formal approval.
Regression tests - Tests the unchanged functions for regression and are typically performed whenever a system update has occurred.
Integration tests - The goal is for all integrated systems to work in harmony. Integration testing verifies that everything works together, including integrated services and data from other sources.
Performance tests - These tests are verified with expected peak load and peak transaction volume and are typically automated and run before go-live.
Migration tests - Practice data migration to ensure data quality. These tests are performed in close consultation with subject matter experts that know the customer data. These experts should understand the data transition and transformation and can confirm that the migrated data is valid with proper context.
Disaster recovery tests - A disaster recovery plan is useless if it doesn’t work.
Go-live tests - Dry runs of the complete solution and go-live process. These tests are typically performed before go-live.
Not all types of testing will be required; it's determined by the size and scope of the project.
Several activities should be performed prior to go-live:
- Performance testing
- Deployment planning
- Risk assessment
When external authentication is used, credentials and password management are handled by external identity providers. Supported authentication protocols include:
- WS-Federation and SAML 2.0
- OAuth2 (Microsoft, Twitter, Facebook, Google, LinkedIn, Yahoo)
- OpenID Connect (Azure AD, Azure AD B2C)
Post a Comment