Best practice for QA testing and UAT

[AllenLM]

[Enter feedback here]
Could you advise what is the best practice for QA testing and UAT for SPFx solutions? like which environment should be used, how to prepare the environments, etc.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6633d599-b172-b752-bc51-62227b08c98c
• Version Independent ID: 262bf4bd-0e61-6c1f-c709-37b56089b622
• Content: SharePoint Framework solutions governance considerations
• Content Source: docs/spfx/web-parts/guidance/governance-considerations.md
• Product: sharepoint
• Technology: sharepoint-framework
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[bcameron1231]

Generally, I just set up different site collections for each environment, and use the Site Collection App catalog to provision to each respective environment.

In rare occasions, I need a whole new tenancy because I'd have applications that may modify global properties, such as User Profiles.

[michaelmaillot]

To complete @bcameron1231's answer, you can check out documentation around Site Collection App Catalog here.

[AllenLM]

@bcameron1231 @michaelmaillot Thank you both.
In our environment, all sites are 'flat', we've created a lot of teamsites for different teams, the URLs of the team sites looks like this:
https://xxx.sharepoint.com/sites/teamA
https://xxx.sharepoint.com/sites/teamB
If I create a site collection for DEV and one for UAT, the URLs should somehow looks like this:
https://xxx.sharepoint.com/sites/DEV
https://xxx.sharepoint.com/sites/UAT
I should be able to create sites under these site collections to test site collection level apps like below:
https://xxx.sharepoint.com/sites/UAT/teamA
https://xxx.sharepoint.com/sites/UAT/teamB
This should work for site collection level apps, but if I am creating a tenant level app which will share accross all the 'flat' sites I mentioned above, how can I testing it in the DEV and UAT site collection without affecting teamA and teamB especially in case of upgrading the app which is already in use by some of the sites directly under tenant?

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.