Discussions

I see that there's a fork project that says it's for VS 2015 and .Net 4.6, but I'm on a project using 4.5, and I can't seem to get SpecsFor.MVC working. The regular version fails to install right, complaining that the browser drivers already exist. I can push past that by trying the install multiple times, but I still don't end up with a SpecsFor.Mvc reference in the project, even though the NuGet package seems to think it should be there. I tried the fork project, but didn't have any better luck there since it wants to reference a higher version of the System.Web.Mvc assembly.

Moq has a way of specifying values for primitive dependencies. Is there any way to explain this to SpecsFor without completely taking over the SUT construction via InitializeClassUnderTest?

I'm on a project now that uses Knockout on the front-end, but I'm hopelessly addicted to SpecsFor.Mvc. I imagine that if the on-page controls follow the same naming convention as MVC would have, then SpecsFor would still be able to find them and use them. As I understand it from the MvcTemplates package, the magic is in wrapping a span around the controls and naming it after the property on the viewmodel. Is this correct? Are there any examples of workable patterns for integrating with Knockout? How about other front-end technologies like Angular?

There is an AfterEachSpec, but no matching BeforeEachSpec. Given and When seem to run once per fixture if I'm not mistaken, or at least they appear to be working that way. I have a specific mock that I want to set up differently for one test. Yes, I know that's technically a new context, and I should build a new fixture, but that's would be so heavy in this case that I opted for a simpler text fixture with the individual tests taking some responsibility for tweaking the mocks. Don't you judge me... stop looking at me like that! I am NOT doing it wrong! Okay, fine, I'm doing it wrong. Anyway, I'm seeing the mock behavior bleed over from one test to another depending on their execution order. What I'd like is to set up the 99% behavior in a BeforeEachSpec, and tweak it in just the one test that deviates.

How can I assert a list, something like below:
myResult.ShouldLookLike(() =>
new List(){
new MyObject(){
//resultId is Guid, so this should be ignore
ObjectName = "result name 1",
ObjectValue = "object value 1"
},
new MyObject(){
//resultId is Guid, so this should be ignore
ObjectName = "result name 2",
ObjectValue = "object value 2"
}
}

Any issues/recommendations/suggestions with using SpecsFor with WCF? I'm using vanilla nunit however i'm really liking SpecsFor and would like to migrate those tests into this framework.

How does this library interact with Theories. I'd like to have multiple datapoints for my tests.

Do you see any issues with using Specs for and Telerik's JustMock mocking library? We have a dependency on it for Fakes of legacy code.

Hi,

Hello