-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding unit tests to validate Tug.Client protocol compliance #32
Conversation
This file contains 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
We use this to setup a local DSC Pull Server which is then used by the unit tests that validate protocol compatibility with our Tug Client (which is then used to test protocol compatibility with our Tug Server).
…ration The property order is significant when using RegKey Authorization!
Replaced non-existent DNS name for test classic DSC Pull Server with a test name that is configured locally (i.e. local hosts file or local CI hosts entry)
Correcting behavior for client response handling and return for *GetDscAction* message.
Adding tests for validating protocol and behavior compatibility between the Tug.Client library and a classic DSC Pull Server (v2).
Adding richer output from methods that handle file content retrieval (GetConfiguration, GetModule).
Adding a new test case to verify the actual expected content and checksum. The test works in tandem with a set of *StaticTestConfig* MOF configuration and checksum objects that are expected to be accessiable from the target DSC Pull Server.
An AgentId is required in the request header, presumably to authenticate the node to the pull server (when using RegKey Authz during registration)
Goes a long way to implementing #25 |
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.
On the CI server, we setup a local DSC Pull Server (xDscWebService) and then run a battery of tests on Tug.Client against this Pull Server to validate the basic MS-DSCPM protocol messages and behaviors.