Forum member

simmdan

13 posts

Posts by simmdan

  1. 'Additional Files To Include' adding Byte-order mark? (NCrunch 1.48)

    Excellent! That fixed my issue.

  2. 'Additional Files To Include' adding Byte-order mark? (NCrunch 1.48)

    Done. Thx.

  3. 'Additional Files To Include' adding Byte-order mark? (NCrunch 1.48)

    Repro solution sent via the contact form, but I can't tell for sure if it got through or not because when I click "submit request" it works for a few minutes and then displays a page that says: Sorry! The page you tried to access does not exist. Click here to return to the home page of NCrunch…

  4. 'Additional Files To Include' adding Byte-order mark? (NCrunch 1.48)

    I will work on getting you a repro/sample file. In the meantime, though, it would be great if there were either some external channel which could be used to tell ncrunch the encoding of the file or even if there was just a way to tell ncrunch to not try to pick up the current in-ide version of a fi…

  5. 'Additional Files To Include' adding Byte-order mark? (NCrunch 1.48)

    I'm encountering this same issue with NCrunch 2.16.0.13 running under VS 2015 in a project using ANTLR4. If I have a grammar file open in the IDE (even if I haven't modified it), then my build fails apparently because the ncrunch workspace is created with a copy of the G4 file that has the wrong en…

  6. After upgrade to 2.14, in-editor status indicators not updating correctly

    Sorry for taking so long to respond (especially after your quick and accurate answer to my initial post). I had this problem all morning the first day when I reported the problem, but I had not shutdown/restarted visual studio all that time. Once I did that the problem went away and has not recu…

  7. After upgrade to 2.14, in-editor status indicators not updating correctly

    Hey Remco, I'm running VS 2013 update 4 with NCrunch 2.14.0.8. I upgraded to 2.14.0.8 a few days ago, but just noticed this morning that the in-editor status indicators (which indicate code-coverage and test status) are not updating properly. Here's the scenario: I have a test which is faili…

  8. Since upgrade to 1.47 handling of test display changed

    By tests window filter being set not to show tests that haven't been executed before, do you mean the eyeball/question mark icon on the toolbar at the top of the tests window? The one whose tooltip says "Show unexecuted tests"? If so, sadly this theory doesn't pan out because I normally leave that…

  9. Since upgrade to 1.47 handling of test display changed

    My integration tests are actually scattered through various test projects in my solution rather than being grouped in a way that would make them easy to filter, so I don't think that was the case. I do have some memory, though, which I think was from a significantly earlier version of the product w…

  10. Since upgrade to 1.47 handling of test display changed

    I've been using NCrunch for some time now with great success. Thanks for such a wonderful product! One of the features I've depended on for a while is the ability to customize engine modes. I modified the default run all tests automatically mode so that it runs all tests except those marked wit…

  11. DeploymentItem results are inconsistent

    Switching to paths relative to the project rather than the sln did fix my duplication problem for resharper, but it doesn't seem to work for the ncrunch runner. So the summary is this: [list=1][*]DeploymentItem with path relative to solution: [list=a] [*] File for the deployment item…

  12. DeploymentItem results are inconsistent

    Hi Remco, Thanks for the quick response. I have read about test atomicity, and I've been careful to avoid making the tests dependent on being run together. Looking back over things this morning I see that the two tests don't actually use the exact same deployment items, but they follow the same…

  13. DeploymentItem results are inconsistent

    I have two unit tests in the same file in the same project which each use the same [DeploymentItem] attributes. Both of them succeed with other test runners (resharper, for instance), but with ncrunch one succeeds and the other fails. The failure comes from the deployment item file not being prese…