Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matthias Koch
    @matkoch
    no test discovery in visual studio or resharper?
    Jake Ginnivan
    @JakeGinnivan
    These are just libraries which sit inside other testing frameworks
    you can use with fixie, nunit, xunit or any others
    Matthias Koch
    @matkoch
    yes, but will never be usable in a big solution
    Jake Ginnivan
    @JakeGinnivan
    how so?
    Matthias Koch
    @matkoch
    or maybe i don't understand..... how are tests displayed in the runners?
    Jake Ginnivan
    @JakeGinnivan
    we output to console/trace/whatever the test framework will pickup and display
    Matthias Koch
    @matkoch
    that's something that should be added to the readme.md :)
    Jake Ginnivan
    @JakeGinnivan
    Possible :)
    Matthias Koch
    @matkoch
    if you don't have any means to browse through test structure, THEN it's not suitable for big solutions
    btw, do you know pendulum? :)
    Jake Ginnivan
    @JakeGinnivan
    Test structure you use same techniques as xunit/nunit/whatever. organise by class or folders/namespaces etc
    nope?
    Matthias Koch
    @matkoch
    noticed you're from Perth... they're also... pretty famous =D
    Jake Ginnivan
    @JakeGinnivan
    oh, band
    haha
    Matthias Koch
    @matkoch
    i will leave it here once again =) https://github.com/matkoch/TestFx hope to get some people to test it
    Reuven Y.
    @robi-y
    This message was deleted
    John-Philip Johansson
    @seriema
    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?
    Jake Ginnivan
    @JakeGinnivan
    @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
    Peter
    @AnderssonPeter
    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?
    Reuven Y.
    @robi-y
    @AnderssonPeter b)
    Jake Ginnivan
    @JakeGinnivan
    @AnderssonPeter it is an assertion library, it can be used with any unit test framework
    matneyx
    @matneyx
    @AnderssonPeter, we use it in conjunction with both Xunit and NUnit with absolutely no issues.
    Dylan Beattie
    @dylanbeattie
    Morning Shouldliers!
    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.
    Jake Ginnivan
    @JakeGinnivan
    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
    Dylan Beattie
    @dylanbeattie
    ah. visual studio has a test runner. of course it does.
    Joseph Woodward
    @JosephWoodward
    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?
    Dylan Beattie
    @dylanbeattie
    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.
    Dylan Beattie
    @dylanbeattie
    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.
    Dylan Beattie
    @dylanbeattie
    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...
    Joseph Woodward
    @JosephWoodward
    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.
    Tom Wright
    @tdwright
    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
    Appears to be a timeout scenario (FuncOfTaskOfTWithTimeoutScenario) timing out: https://ci.appveyor.com/project/shouldly/shouldly/build/2.8.3-PullRequest.406+7.build.289/tests
    João Barbosa
    @bmpj13
    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:
    Jake Ginnivan
    @JakeGinnivan
    Hey, will get back to you today with details and info
    AdityaTulasi
    @AdityaTulasi
    Hi. I'm too am interested in contributing. Please send that e-mail to me as well.. E-mail ID tulasiaditya1993@gmail.com
    @bmpj13 Can you please forward the e-mail of instructions you get for contributing?