Feature/testing environment#6996
Conversation
- M365DSCDeploymentTestEngine.psm1: Core engine that deploys each resource, exports tenant state, and uses Assert-M365DSCBlueprint for drift detection - Supports all auth methods (Credential, Certificate, AppSecret, ManagedIdentity, AccessTokens) - Auto-detects supported auth methods per resource from schema MOF files - Config/TestTenants.config.json: Tenant config with env var placeholders for secrets - Config/KnownIssues.json: Registry of resources with known deployment issues - Helpers/Get-ResourceAuthMethods.ps1: Auth method discovery utility - Helpers/New-TestReport.ps1: HTML/JSON report generator - Helpers/Invoke-TenantCleanup.ps1: Tenant reset utility - GitHub Actions workflows for per-workload and all-workload deployment testing - README.md with full documentation and usage examples
nandhakumar1980
requested review from
FabienTschanz,
M365DSCApprover,
NikCharlebois,
m365dscapproval and
ykuijs
as code owners
|
microsoft-github-policy-service @microsoft-github-policy-service agree |
|
@microsoft-github-policy-service agree |
|
@nandhakumar1980 Thank you for the PR. The proposed testing environment is a change too big to handle right now since we already have a couple of tests running at the moment, but we'll leave it open and adapt certain aspects of it into our testing to improve the quality of the product. Appreciate it. |
|
@FabienTschanz This is what I've been doing for years, but I use my own code. I could still share with you privately all the blueprints I've carefully created manually, I shared them with Nik a long time ago also but the current pipelines here in GH already started this work but actually don't work because they use credentials and without MFA they don't work, my blueprints on the other hand use certificates (where I use my own variables instead of relying on ConfigurationData). |
|
@ricmestre I'm aware of that fact. I'd first like to implement some changes here to target my own lab tenant for this, and once that is done, I can start with implementing more examples. I'll message you privately for some information when I get to the point where I need them. Thanks. |
|
@FabienTschanz Thanks for the feedback! That makes sense. Would you prefer if I break this into smaller PRs or focus on specific parts that align with your current testing setup? Happy to adjust based on what works best for the project. |
3 participants
Description
This PR introduces incremental improvements to the existing testing setup while preserving the current structure and workflow.
The focus is on improving maintainability, organization, and test execution without introducing disruptive or large-scale changes.
Changes
M365DSCDeploymentTestEngine.psm1) to support test executionWhy this change?
A previous proposal introduced a broader testing overhaul, which may be difficult to review and integrate in a single step. This PR instead focuses on smaller, self-contained improvements that align with the current setup.
Benefits
Notes
These changes are intended to be incremental. Additional improvements can be proposed in follow-up PRs if needed.
-->
Entry should say what was changed and how that affects users (if applicable), and
reference the issue being resolved (if applicable).