Using the Unit test Runner with NUnit

4 posts, 0 answers
  1. Rafal Tynski
    Rafal Tynski avatar
    13 posts
    Member since:
    Oct 2009

    Posted 23 Sep 2010 Link to this post

    HI.
    I have problem with learn http://tv.telerik.com/watch/justcode/using-unit-test-runner-with-different-test-frameworks
    When I try test i get Build Failed. When i look on the Show Output from JustCode I not have nothing.
    Where I find reason this problems.
    Thanks.

    I have last version.
  2. Deyan Varchev
    Admin
    Deyan Varchev avatar
    150 posts

    Posted 04 Oct 2010 Link to this post

    Hi Rafal,

     Thank you for contacting us. When the build fails it is usually because the compiler cannot finish successfully building the source code. You can see the reason for the build failure either in Visual Studio's Error List window (in your screenshot it is right next to the Unit Test Window), or in the Output window. If you want to see the compile output you need to select "Build" from the dropdown list at the top of the Output window. 

     If you have any other questions or problems, contact us again. 

    Sincerely yours,
    Deyan
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. DevCraft banner
  4. Rafal Tynski
    Rafal Tynski avatar
    13 posts
    Member since:
    Oct 2009

    Posted 07 Oct 2010 Link to this post

    This problem been when i have few projects. And one have error build.
    I not use this project for test.
    I have test other project and i don't have.
    I must unload this project and start test again.

  5. Deyan Varchev
    Admin
    Deyan Varchev avatar
    150 posts

    Posted 19 Oct 2010 Link to this post

    Hello Rafal,

     Thanks for clarifying the case. Currently JustCode's test runner is building your whole solution and not only the projects that your tests directly depend on. The reason for this is that there could be other projects that affect tests as well - i.e. when reflection is used or dlls are loaded dynamically by MEF or other similar frameworks. However we are looking at this issue and hopefully will have a better solution with some configuration options soon.

    All the best,
    Deyan
    the Telerik team
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
Back to Top