Forum member

tlianza

11 posts

Posts by tlianza

  1. no stack traces when test fails

    [quote=Remco;1500]Hi, thanks for coming back to this! My suspicion is that there is something in your test environment that is causing the test runner to bomb out. The easiest way to identify the cause of this problem is to turn on the logging in NCrunch. You should find a setting to control this…

  2. Extension methods not present when debugging

    When I'm debugging a test in ncrunch, if I try to inspect a System.Linq.IQueryable and then call ToList() on it in the QuickWatch tool I get: 'System.Linq.IQueryable<MYTYPE>' does not contain a definition for 'ToList' and no extension method 'ToList' accepting a first argument of type 'System.…

  3. no stack traces when test fails

    [quote=Remco;750] You may be able to get more information about why the test failed if you set your logging to a more verbose level (i.e. Detailed), then find the task that was used to execute your tests in the processing queue. It will be a bit noisy, but the answer should be in there.[/quote] …

  4. no stack traces when test fails

    [quote=Remco;744] As far as NCrunch is concerned, the parent fixture will always be the fixture that is shown above the test in the test tree view. If the test throws an exception in a TestFixtureSetUp, you should always see the stack trace on this node ... if not, then it's definitely a bug! :) …

  5. no stack traces when test fails

    [quote=Remco;742]Hi Tom, In this case, the test failed because its parent fixture failed on setup. If you choose the parent fixture in the tree view, it should show you the stack trace. NCrunch has a strong distinction between fixtures and tests, as mechanically they behave very differently. …

  6. no stack traces when test fails

    When a test fails, this is all I see: [img]http://content.screencast.com/users/tlianza/folders/Jing/media/ce4bae46-acd7-473a-96cc-dbdbfe6b93c9/2011-12-14_1808.png[/img] (http://screencast.com/t/3YlKTb53RqF) In the Nunit gui, I'd also get the stack trace, so I'd have some shot at telling wha…

  7. nCrunch doesn't build test project, as if it doesn't know about references

    [quote=Remco;738]Thanks again. It looks as though the TeamAgile.XtUnit project isn't included in the same solution as your test project. Is this the case? Right now NCrunch has a known issue with building against references to projects outside the current solution. It's on the list of things t…

  8. nCrunch doesn't build test project, as if it doesn't know about references

    [quote=Remco;736]Thanks. As the bug report only contains a limited log capacity, I'm wondering if you might be able to give me a fresh capture. Would you be able to do a complete reset of NCrunch (disable/enable) then submit the report as soon as all the builds complete?[/quote] Done.

  9. nCrunch doesn't build test project, as if it doesn't know about references

    [quote=Remco;733] Would you be able to show me how these files are being included in your build? (i.e. copy/paste of the one of the <Reference> tags from your project file would be great). Are you using any known build customisations or packaging frameworks? (i.e. Nuget, Openwrap, etc)..[/quote]…

  10. nCrunch doesn't build test project, as if it doesn't know about references

    [quote=Remco;730]Hi Tom - Thanks for reporting this issue. Would you be able to submit a bug report using the 'NCrunch' menu as soon as this issue occurs? It looks like a resolution problem inside the engine. Cheers, Remco[/quote] Done! Also included a link to this forum post in the …

  11. nCrunch doesn't build test project, as if it doesn't know about references

    Hi All, I have a project of nUnit tests in my solution, and though nCrunch can build most of my projects, it fails on this one with errors like this: Agent\JobDispatcherTest.cs (10): The type or namespace name 'TeamAgile' could not be found (are you missing a using directive or an assembly ref…