Add integration test stage for DSCv3 #2102
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It runs now, but fails with: |
johlju
added
the
waiting for author response
|
This is the full trace log from the pipeline. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2102 +/- ##
====================================
Coverage 94% 94%
====================================
Files 106 107 +1
Lines 8089 8147 +58
====================================
+ Hits 7650 7709 +59
+ Misses 439 438 -1
🚀 New features to boost your workflow:
|
|
With latest preview6 it goes further, but errors on Get it seems. The output from {
"type": "SqlServerDsc/SqlRSSetup",
"kind": "resource",
"version": "17.2.0",
"capabilities": ["get", "set", "test"],
"path": "D:\\a\\1\\s\\output\\builtModule\\SqlServerDsc\\17.2.0\\SqlServerDsc.psd1",
"description": "This module contains commands and DSC resources for deployment and configuration of Microsoft SQL Server, SQL Server Reporting Services and Power BI Report Server.",
"directory": "D:\\a\\1\\s\\output\\builtModule\\SqlServerDsc\\17.2.0",
"implementedAs": "ClassBased",
"author": "DSC Community",
"properties": [
"AcceptLicensingTerms",
"Action",
"InstanceName",
"MediaPath",
"DependsOn",
"Edition",
"EditionUpgrade",
"ForceRestart",
"InstallFolder",
"LogPath",
"ProductKey",
"PsDscRunAsCredential",
"SuppressRestart",
"Timeout",
"VersionUpgrade"
],
"requireAdapter": "Microsoft.Windows/WindowsPowerShell",
"manifest": null
}The content from the file |
|
The tracelog from the test run: |
…owerShell version output in integration tests
…gine integration tests
…Engine integration tests
Closed
3 tasks
…ugDscEngine integration tests
…ugDscEngine class
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Now it actually returns a result, but the read-only property is not returned: |
|
It seems that first the first test that is run, read-only property is not returned in the output, but when the second test is run it does return the read-only property. Shifting the first and second test the test that first worked will fail and vice-verse. So there is something happen on the first time running the dsc executable with a class-based resource that does not do what it should. 🤔 Test 1 tracelog: Output from Pester 5: Test 2 tracelog: Output from Pester 5: |
…cases and enhance verbose logging
…DebugDscEngine integration tests
|
The issue now that it fails seems that we have run this prior to running the tests: dsc resource list --adapter Microsoft.Windows/WindowsPowerShell |
|
Labeling this pull request (PR) as abandoned since it has gone 14 days or more since the last update. An abandoned PR can be continued by another contributor. The abandoned label will be removed if work on this PR is taken up again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
This Pull Request (PR) fixes the following issues
Task list
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
This change is