I like the shouldly syntax a lot, but I'm wondering if there's a way to make them stand out a bit. When quickly scanning through test code it's hard to see what is the "assert" compared to "act". In JS and mocha the BDD syntax is: expect(myvar).to.be.null; The dot syntax isn't interesting, but the "expect()" is very helpful even if it can seem like unnecessary code.
I guess one way would be a generic Expect() method that just returns the param. Has anyone experimented with or seen what I'm looking for?
@seriema not sure there is much in that space. Assert. style libraries like xUnit assertions probably match what you want better.
TBH I just sometimes use // Assert in my tests to separate it
I have been looking at shouldy and it seems nice i just have one question, does this replace other unit test frameworks like mstest and xunit or does it just enhance them?
@AnderssonPeter it is an assertion library, it can be used with any unit test framework
@AnderssonPeter, we use it in conjunction with both Xunit and NUnit with absolutely no issues.
I've a question - what test runner should I use for running the tests in the latest master? My usual runners are NCrunch and Resharper and although the solution builds just fine, neither of them can find any test assemblies.
Visual studio :(
its the only one which supports dotnet test
command line also works if you run dotnet test in the test project folder
or run build.ps1 to build and test everything
Never though id be saying, am looking forward to them switching to msbuild
ah. visual studio has a test runner. of course it does.
JetBrains say it shouldn't be long until ReSharper's test runner supports .NET Core
@dylanbeattie Did you get to the bottom of that issue you mentioned on Twitter yesterday?
I'm looking into it now.
OK, how do I add a project reference to Shouldly from a .NET 4.5.1 class library project?
I want to be able to step into Shouldly's assertion code from the test that's failing to find out why, but I cannot seem to get them running happily in the same solution.
ok, got it... for some reason VS won't add a project reference but by adding a DLL reference directly it's letting me step into Shouldly code.
It's not a Shouldly issue. It's to do with Object.Equals(x,y) returning false if x and y are similar anonymous type instances that have come from different assemblies...
That's interesting, didn't know that was the case.
Shame you can't create a PR to the MSDN docs to stop others getting tripped up by this in the future.
Hi all. I'm hoping to try and get involved as a contributor. Thought I'd start with a couple of small issues. Problem is, I appear to have broken the build before going any further than a couple of markdown files. Any idea what's going on? shouldly/shouldly#406
Hello everyone. I'm also interested in helping as a contributor. @JosephWoodward , I sent you an email so I could get a bit more of information about the project (I didn't want to spam the chat). Hope everyone's doing fine :smile:
Hey, will get back to you today with details and info