Discussions

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?

I'm trying to write a spec for a class that takes as its ctor parameter an IEnumerable object. I'm overriding ConfigureContainer and specifying a List of real objects however the sut isn't seeing those values. Any ideas?

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.

Want to run tests in VSTS. No tests seems to be running.

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"
}
}

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.

Are there any examples of using SpecsFor with NUnit's RowTests? (Now called TestCase, I believe)