Common test to verify mofs compile should be run as an it-block about dscresource.tests HOT 11 CLOSED

I'm working on this one as well.

from dscresource.tests.

@PlagueHO I have this finished and have tested it on xSQLServer. But would like to test it on a few other modules before sending in the PR. Do you have a suggestion for modules worth testing on. Thinking you done a few rounds of testing already so you would now the best modules to test on. 😄

from dscresource.tests.

Hi @johlju - I've tested/done the following:

• xNetworking - complete and PR submitted (waiting review).
• xStorage (but also moved it over to the new xNetworking/SharePointDsc layout with Autodocumentation). However, the Pester 4.0.2 bug prevents the tests from failing so I can't submit till it's fixed.
• xCertificate - I will do this one, but I'm still in process of implementing the Cert Export resource so I'll complete the changes to this in parallel.
• xDFS - I've tested this one, but I'm moving to Autodocumentation in the xNetworking/SharePointDsc style.
• xComputerManagement - I've tested this one - but Pester 4.0.2 bug also causes problems.

I plan to do xADCSDeployment as well as some others as soon as I can. I think the tough ones will be xActiveDirectory and xWebAdministration. It is possible @tysonjhayes is working on xWebAdministration though - so might be worth checking with him on that one.

The Pester 4.0.2 bug(s) - pester/Pester#697 - are causing many problems with existing repos. So even without the changes to DSCResource.tests, many repos are going to have problems. @kwirkykat and @mbreakey3 I think made changes to a couple of repos to force an older version of Pester to be used.

from dscresource.tests.

@johlju - one further thing on this: it might be a good idea to raise an issue on each repo that we're currently moving over to this new model so we don't duplicate work.

from dscresource.tests.

@PlagueHO I will test my changes on xNetworking and SharePointDsc, which have examples and currently are working (not sure about SharePointDsc). For now I just want to test the examples test changes I did.

@PlagueHO I think if we start fixing to the new pattern in a repo it would be good idea to add an issue. If there is no issue then nobody is working on it. :)

from dscresource.tests.

@PlagueHO Well that did not work to test in those. Since the use the harness. :) I send in the PR anyway and we'll see what you think of it.

from dscresource.tests.

I am working on xWebAdministration, been sick the last few days so I'm a bit behind. 😁

from dscresource.tests.

@tysonjhayes - Hope you're feeling better bud! 😁

@johlju - my fork of xStorage uses Harness as well. My fork of xComputerManagement doesn't though. You could try that one? It also has examples that have credentials etc so it would be a great test I reckon.

from dscresource.tests.

@PlagueHO I will test your branch of xStorage tomorrow!

from dscresource.tests.

@johlju - cool! I've forced my xStorage branch to use the older Pester version (without all the bugs):
https://github.com/PlagueHO/xStorage/tree/Use-AppVeyor-Module

from dscresource.tests.

@PlagueHO Work like a charm: https://ci.appveyor.com/project/johlju/xstorage/build/2.9.1.0#L726

from dscresource.tests.