Forum member

alexnorcliffe

23 posts

Posts by alexnorcliffe

  1. Suggestion: Add an integration with an R# plugin to allow running a test using nCrunch manually

    That's fine and understood, I'm doing the same with our own framework for the same reasons (trying to guide people only to the bits that are settled) The rather thinly veiled offer is for help and collaboration though, which I've made a few times, so have another think about it :) Maybe Marcel woul…

  2. Move coverage markers slightly to avoid conflicts with R# jewels

    D'oh sorry late night writing - I meant right. Anyway, think I've made my point :)

  3. Suggestion: Add an integration with an R# plugin to allow running a test using nCrunch manually

    OK that makes sense... so long as the other issue I mentioned is solved to ensure the summary marker doesn't conflict with R# markers :) I could always knock-up an independent R# plugin myself I suppose, but I'd need some hints on which nCrunch.Framework(?) methods to call to kick off a test run,…

  4. Move coverage markers slightly to avoid conflicts with R# jewels

    How about taking R#'s approach - move to the left, but perhaps with some transparency unless the mouse is nearby

  5. Suggestion: Add an integration with an R# plugin to allow running a test using nCrunch manually

    I use R#'s test runner alongside nCrunch. It would be great if an option to "Run test using nCrunch" appeared in the R# jewel that it already displays next to each discovered test I checked with Hadi about the feasibility, here's what he had to say: [17:57:01] Alex Norcliffe: ping, 2 min quest…

  6. Move coverage markers slightly to avoid conflicts with R# jewels

    Sometimes R# puts its lightbulbs etc. over the top of NCrunch markers. Seems there's greater chance of success asking for NCrunch to move them slightly than having R# do it ;)

  7. Allow "Debug" runner mode by telling VS to attach to the test runner

    Works awesomely, btw. Great feeling to see a feature req make it into the product so quickly (this past 6 months has flown by)

  8. NCrunch does not responde at all

    Was just about to post the same issue. I had to do a hard reset on my machine and was getting VS giving an error saying that the nCrunch extension didn't initialize properly. After a lot of uninstalling / reinstalling (not nCrunch's fault - I was getting other errors too) I happened to notice tha…

  9. Any docs for NCrunch's AppDomain setup? (Ref running tests in Medium Trust from BoxBinary.com)

    Going off the feedback I've got for the post series so far, it's not an area that's well exercised full stop really. I devised the solution to avoid us having extension methods / library usages creep into our codebase that unwittingly don't support Medium Trust (e.g., the Clone() method I use as an …

  10. Any docs for NCrunch's AppDomain setup? (Ref running tests in Medium Trust from BoxBinary.com)

    I recently implemented a method for running tests in a Medium Trust context (part three here (- BROKEN LINK -)) It's working great for us in R#, NUnit and TeamCity's runners. This involves setting up a new AppDomain loading the PermissionSet from the web_mediumtrust.config, and invoking the te…

  11. TestCaseSource attribute incorrectly requires TestCase attribute, not Test?

    Does the same apply to Value and Range parameter attributes? Marking a test with TestCase actually runs each range, but with Test it doesn't even identify that it's a valid test (black dots) Likewise, this is actually invalid as it should be a Test attribute (to make it work in R#6 and NUnit runne…

  12. Build runner does not support inline dynamics e.g. var myObject = blah.MethodWhichReturnsDynamic()

    Here you go. Stick this function in one assembly: public static dynamic MyFunction() { return string.Empty; } Stick this in another assembly - 1.33b fails to build although VS builds it fine: dynamic myObject = MyClass.MyFunction().Empty; …

  13. TestCaseSource attribute incorrectly requires TestCase attribute, not Test?

    Sticking this on the forums in addition to the "submit bug report" in case others are getting this, or I'm doing it wrong :) I've noticed that to use TestCaseSource NUnit attributes with NCrunch, you have to also decorate the test with the TestCase attribute. The NUnit docs (http://www.nunit.org/…

  14. Build runner does not support inline dynamics e.g. var myObject = blah.MethodWhichReturnsDynamic()

    Only just noticed your reply! Will take a look now

  15. Stack overflow / infinite runtime of a test causes NCrunch 1.33b to fail

    I reckon I've spotted a part of the prob: I was running the tests in linear fashion, now that I've switched to running tests in parallel NCrunch does appear to kill the recursive test eventually and recover.

  16. Allow "Debug" runner mode by telling VS to attach to the test runner

    Despite 1.33b being awesome, I'm using it in parallel with R# 5.1's runner at the moment because it has some killer features, one of which is debugging a test. NCrunch's red cross markers to say exactly where the code failed are brilliant, but the tooltip is tricky (really small mouse hit area an…

  17. NCrunch 1.33b crashes when test method contains neverending recursion

    Oops looks like I might have posted a duplicate http://forum.ncrunch.net/yaf_postst70_Stack-overflow---infinite-runtime-of-a-test-causes-NCrunch-to-fail.aspx However, for me NCrunch didn't carry on as usual :) It would even be a good iterative improvement if the NCrunch engine gracefully handled a…

  18. Stack overflow / infinite runtime of a test causes NCrunch 1.33b to fail

    Great work on 1.33b, massive improvement! If a test causes a stack overflow, or just never returns, the NCrunch runner never returns either. Clicking the 'Reset' button in the Tests panel, or Disabling / Enabling NCrunch from the VS menu, appears to cancel the test run as the tool panels get clea…

  19. Build runner does not build Web application projects

    Legend - really good of you to take a look at the solution, thanks! I've been using NCrunch 1.33b and didn't realise you'd replied to this thread, I actually came back to say it's awesome and help you out with a couple more bug reports :) In the meantime for those tests with the missing config file…

  20. Build runner does not support inline dynamics e.g. var myObject = blah.MethodWhichReturnsDynamic()

    Thanks for taking a look at this! For now I've just explicitly declared the offending variables as 'dynamic' rather than implicit typing, as the NCrunch instrumentation is more valuable :)