Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. (v1.37b ) New feature request: go to the location of the actual error, the deepest statemen

    If you haven't given it a try yet, the exception popup window (left click one of the Xs) is a very useful way to navigate to the failure point of a particular test. Thanks for the suggestion on the break into option - I'll look into it.

  2. (v1.37b) Issue: go to test does not work

    Hi, Thanks for reporting this - it is a known issue with test files that use collapsed regions. A fix will be in a later release. Cheers, Remco

  3. How do I use with typemock?

    Yes - NCrunch does have issues with the RecordExpectations syntax. The instrumentation placed by NCrunch is causing TypeMock to make incorrect assessments about your test expectations. There are two ways you can work around this: 1. Avoid using RecordExpectations - This is the best option but…

  4. Licensing

    Hi Jason - As it's still a beta product right now, NCrunch is distributed under a closed source free usage license - so all within your team are very welcome to download it and share it as they like. Any future commercial licensing is still TDB. Cheers, Remco

  5. Larger font for Risk bar

    Thanks for the feedback - I'll take a look at it :)

  6. v1.37b - Debug variables

    Interesting ... this is probably caused by the instrumentation. I'll need to take a closer look to figure out why it's happening and if it's preventable. Thanks for letting me know.

  7. Hard Drive usage going up

    Hi Greba, Thanks for sharing the details. I'm wondering if you might be able to confirm for me whether you're doing any cross process testing or anything that might hold file locks on the workspaces? One way to confirm this is if you go through some of the instructions above, but after closing …

  8. Use in solution with VC++ project

    Hi Pedro, At the moment NCrunch doesn't support C++ projects. The best workaround I can offer would be to avoid creating project references to C++ projects inside your solution - use assembly references instead. Using the IDE, delete all references from other projects in your solution to your C…

  9. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    What happens if you try the following? <DefineConstants>DEBUG</DefineConstants>

  10. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    Thanks for the prompt response. A workaround to the problem would be to make sure the opening and closing tags are both on the same line in the source .proj file. I'll make sure a fix is included in the next release for this. Cheers, Remco

  11. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    Would either of you guys be able to show me the DefineConstants tag after it's been corrupted by NCrunch? You can find this by doing the following: - Let the build fail with the error - Right click the failed project in the Tests Window, go to Advanced and choose 'Browse to workspace' - Look fo…

  12. How do I use with typemock?

    Hi Pete, Thanks for posting! NCrunch should auto-detect TypeMock and host it in the task environment. Are you able to provide any more information about how the tests are failing? If you're able to submit a bug report after your tests fail, this would be very useful in identifying why it's not w…

  13. Hard Drive usage going up

    NCrunch will generally clean up workspaces when the process exits, but sometimes this is impossible (due to locks being held on the files by background processes etc). To prevent the drive from getting cluttered, NCrunch will automatically clean up any leftover workspaces when it is restarted and …

  14. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    Ouch - is there any chance I could get a copy of that DefineConstants tag?

  15. Problem with NUnit TestCase attribute

    I understand the perspective, but this could cause considerable confusion - as the test actually did run and does also exist. Tests that are ignored by NCrunch are basically screened out at the analysis stage - as far as the result of the system is concerned, they don't exist. Unless a third sta…

  16. NUnit Assert.Ignore causes failed test

    Hi, thanks for posting. The reason for this is that NCrunch doesn't make use of an 'Inclusive' status to define tests that make use of Ignore. There's some more information about plans here in this thread: [url=http://forum.ncrunch.net/yaf_postst11_Problem-with-NUnit-TestCase-attribute.aspx]http…

  17. Problem: no exceptions seen, no X symbols with Nunit

    Thanks! I see a fix that needs to be applied here. I'll see what I can do about getting it into the next version. If you're able to set your tests to run with an EN culture, it should pick up the stack traces correctly until I can fix the issue - though I'm not sure if this will cause other proble…

  18. Problem building a project with custom BeforeBuild target

    Hi Igal, Thanks for posting! The pre/post build event suppression at the moment only applies to the pre/post build event properties. To suppress the beforebuild/afterbuild targets, you simply need to apply an MSBuild condition to them, as such: <Target Name="BeforeBuild" Condition="$(NCrunch)…

  19. Problem with NUnit TestCase attribute

    Yes - you are correct. NCrunch currently doesn't have a status to identify tests as being inconclusive - if they are inconclusive, it simply assumes a failure. My current plan in this area is to implement a configuration option that lets you control whether an inconclusive test should be conside…

  20. Problem: no exceptions seen, no X symbols with Nunit

    Hi - thanks for reporting this problem. It looks as though NCrunch isn't taking into account the localisation of your stack traces. Could you let me know anything more details about your current locality/culture? Do you have the culture set globally (i.e. in your O/S) or is it just within the t…