Skip to content
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

Merged
merged 33 commits into from
Jan 3, 2017

Conversation

ebekker
Copy link
Collaborator

@ebekker ebekker commented Jan 3, 2017

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.

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)
@ebekker ebekker merged commit de23664 into master Jan 3, 2017
@ebekker
Copy link
Collaborator Author

ebekker commented Jan 3, 2017

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant