(GH-50) Specs to verify Chocolatey Package Dependency

[gep13]

• Closes Final sweep and cleanup of wiki articles #50

[gep13]

@ferventcoder before you say anything...

This isn't pretty, and I know it isn't pretty, but I wanted to get something out there in the last few minutes I had on the computer before switching off for the night 😄

In general, what are your comments on the approach? Couldn't think, off the top of my head, a nice way to Mock to package and it's dependencies in a re-usable way, hence the duplication of the various elements.

If we go ahead with something like this, we should probably do something for testing existence of dependencies that don't have a version, and possibly others as well.

[ferventcoder]

can we leave out framework here? :)

[gep13]

I don't think so. I notice that you left it in as well, so guessing there wasn't a way without it?

[ferventcoder]

This isn't pretty, and I know it isn't pretty, but I wanted to get something out there in the last few minutes I had on the computer before switching off for the night 😄

It's actually not that bad.

[ferventcoder]

In general, what are your comments on the approach? Couldn't think, off the top of my head, a nice way to Mock to package and it's dependencies in a re-usable way, hence the duplication of the various elements.

Context() is overridable in each spec class, this is likely a good place to do that. That way you have 1 IPackage setup and each class takes the base context and determines how it will go by overriding Context(). Then you are not creating a bunch of unreusable logic in the base class.

[ferventcoder]

I'll take this and update it so you can see what I mean.

[ferventcoder]

Here you go sir, take a look - 1cdcb06