Question about testing and mocking about webadministrationdsc HOT 3 CLOSED

Very interesting question. It's always a compromise between what you can test and what you should mock. In the spirit of discussion PowerShell/DscResources#9 I would recommend the following:

• Separate tests to Unit Tests and End-To-End tests.
• Mock all API calls that can harm user machine configuration in Unit Tests.
• Use try { Setup ... } finally { Cleanup } pattern in End-To-End, to make sure that End-To-End tests don't harm user machine configuration.

In our CI system we would run all the tests (machine would be blown away every time), but we also want enable local test runs, so it's important to cleanup everything.

from webadministrationdsc.

I decided for myself to do mostly real testing rather than mocking, because that doesn't prove anything. In huge projects mocking can be a real time saver, but I think we should really test the resources we are writing.

from webadministrationdsc.

My only suggestion here would be that you place this in the integration folder. This way people can avoid running the tests if they are worried about something breaking on their own dev machine (I run all tests every time I publish a change for example).

from webadministrationdsc.