Forum member

jeremygray

32 posts

Posts by jeremygray

  1. Association of non-code (and other undetected dependency) files with tests

    It would be very useful if one could associate with a given test (or fixture or what have you) one or more files (perhaps via a test or fixture attribute including the dependency's relative path or somesuch) for use when NCrunch cannot be expected to detect the dependency between test and file. The …

  2. Larger font for Risk bar

    For what it is worth, I love being able to place the big green graph on a part of one of my side monitors. Please keep it around in at least some form. :)

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

    I can confirm that TestCaseSource is working nicely for one of the new tests I wrote to take advantage of it. There's nothing quite like generating 8000+ test cases dynamically. :)

  4. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I have yet to see this issue re-occur, but I've not been making many, if any, of the kinds of edits since 1.35b that I was doing with the earlier versions. I'll let you know if something does pop up but in the meantime 1.35b is working nicely.

  5. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Thanks for the update. I'll keep my eyes peeled for 1.35b.

  6. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Perforce, actually/sadly/happily/etc., so much the same in the file locking department.

  7. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Following up after my latest submitted bug report regarding this issue: After NCrunch failed while editing a non-code file, editing a code file in the project resulted in no change in the NCrunch build failed status, regardless of whether or not the source change I made could be built (the first and…

  8. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Using 1.34b I have yet to see this problem rear its head for normal code file changes, but it is still causing problems when editing non-code files that are included in projects, even things like text files which have no build action, not even to be copied in as content! Luckily, my bug submission a…

  9. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Cool. I'm off today but will be sure to check it out first thing tomorrow.

  10. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Excellent! Out of curiosity, can you provide any insight into what you think is going wrong?

  11. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    CopyReferencedAssembliesToWorkspace is false for all projects in the solution. (For all projects the default test timeout of 60000 is assigned, instrumenting of the assembly is enabled, and pre/post build event running is disabled.)

  12. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    41 projects. Approx 120k lines (as measured by VS 2010 code metrics), 68k of which are spread almost evenly across two of the 41 projects. The rest of the projects range between a few hundred lines and a few thousand lines. Only around 2200 of the total lines are in tests, spread across a couple of …

  13. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Today's variation :) - editing a form in a designer. As an additional note, in all of the cases I have described so far, "changing the file affected should cause it to resync and carry on" has never worked for me. I have always had to tell NCrunch to resync.

  14. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Sorry, not yet as I've been tied up with other things. Once things settle down I'll see what I can do about that.

  15. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Here's today's example (which I also saw yesterday but hadn't had a chance to mention until now): NCrunch just went from green into red with a Build error (that includes no details in the lower pane of the NCrunch Tests window) after I edited a text file that just happens to be in the project for co…

  16. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I just had the issue crop up again this morning, but this time around it was simple typing of a new statement into an existing source file that NCrunch had just happily built. Clicking on the relevant project in the NCrunch Tests window shows nothing in the lower pane. On a somewhat related note,…

  17. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Some copy/paste/edit from existing members and plenty of Alt-Enter in R# to, for example, update a class' implementation of an interface to account for new signatures on the interface.

  18. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I just ran into this issue again while adding signatures to a number of tests, then interfaces, then implementations. While in the midst of this NCrunch was rightly showing a Build error in one or more projects. Upon completing the last update (after which the IDE was happy to build the solution) NC…

  19. Tests are not recognized

    Nice!

  20. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    Since upgrading from 1.32b to 1.33b this morning I have seen it momentarily fail to build an assembly on two occasions (a different assembly each time.) When this happens, the NCrunch Tests window shows the assembly with a red X. Clicking on that entry does not show any related text in the lower pan…