Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. UnitTest project fails to build

    Something is different about the way your assembly is signed. Would you be able to submit a bug report using the 'NCrunch' menu at the top? I'll take a look at the log file and let you know how to work around it .. most likely you're using some kind of signing approach that isn't supported yet.

  2. Failed to run XUnit tests

    Did the log under any of the test tasks show anything interesting that could indicate a failure? Otherwise, kick through a bug report and I'll take a look at it.

  3. UnitTest project fails to build

    What happens if you enable the option for ALL of the projects in your solution? The next thing would be to check the contents of the build output directory for your test project. You can easily find this by right clicking on the failed project in the NCrunch Tests Window, then under 'Advanced', …

  4. Failed to run XUnit tests

    There are a few things that can cause this. The easiest way to diagnose this issue is to set your log verbosity to detailed then have a look at one of the testing tasks inside the processing queue. The log will usually contain the issue... it could be an internal problem with NCrunch.

  5. Failed to run XUnit tests

    Hi Alex, It looks like this project has a custom build step that executes Xunit tests? Likely you would want to disable this for NCrunch builds by making whichever build target triggers it conditional. You can use the $(NCrunch) environment variable - for example: <Target Name="XUnitTarget" …

  6. UnitTest project fails to build

    Hi Sam, Thanks for posting! This problem is caused by a special build step used to generate the accessors you have defined in your test project. It's unfortunate that these accessors attempt to manipulate assemblies in such a way that prevents NCrunch's build optimisations from working properly.…

  7. Tests inconsistent with Pass/Fail status

    Hi John, Thanks for the feedback. I've been thinking about this problem a bit and I'm considering a simple change that might make the behaviour more obvious. Right now NCrunch has two main options to run tests - one will run the tests in an existing process, the other will run them using a ne…

  8. Larger font for Risk bar

    Good thinking - removing those bevels makes an amazing difference... I'll see what I can do here. Sadly replacing the express tree with a ListView isn't an option. The express tree has a huge range of features that really are necessary to be able to display the tests in a meaningful way. Someth…

  9. Donations?

    Maybe I can make you happier by sharing another release? :)

  10. New feature (cosmetical) request

    Thanks for the feedback. You'll notice that to an extent, this is already possible. If you click on the exception X, you'll see a popup that shows the full stack trace for all covering exceptions, along with a pane down the bottom that shows the exception message.

  11. (v1.37b) yellow marker for slow tests issue

    Am I correct in my understanding that you want to disregard any performance metrics that are derived from a failed test? I guess the only way I could see this working is if NCrunch were to separate the performance information from the code coverage ... this could be quite confusing if you were hove…

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

    Taking a look at the build process for VB, I can see now why this is failing. It seems VB has a completely different workflow for the DefineConstants than other .NET languages. Can you give me any details regarding what you are using DefineConstants for in this project? Perhaps I can find a diffe…

  13. Add ability to exclude files from coverage scanning

    This is a good idea. Thanks for sharing it :)

  14. Hard Drive usage going up

    Nice testing - that is a very useful piece of information. I'll see what I can do about arranging a fix.

  15. (v1.37b) yellow marker for slow tests issue

    Thanks for posting. Could you share your thoughts about how such a change would be useful to you? Sometimes exceptions are actually raised as normal behaviour in programs and it would be useful to be able to establish the performance penalty for this.

  16. (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.

  17. (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

  18. 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…

  19. 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

  20. Larger font for Risk bar

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