Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Build Errors Needs Details and New Window
Options
Previous Topic Next Topic
CreepyGnome
#1 Posted : Wednesday, August 22, 2012 5:22:09 PM(UTC)
Rank: Member

Groups: Registered
Joined: 8/21/2012(UTC)
Posts: 22
Location: Arizona

Thanks: 2 times
Was thanked: 5 time(s) in 5 post(s)
When a project fails to build and you click on the NCrunch circle in the status bar it takes you to the NCrunch Tests window and shows regular projects with a Bx icon. You can select them but there is no messages as to what the build error(s) where. As I can build the solution just fine but NCrunch can't built a project or two everyone in a while and it wont tell me why.

Also when non-test projects have build errors why does it take me to the NCrunch Tests window? They are not Tests that are failing.

I would recommend that you have a different error window for when there is non-Test issues, and that you provide the build output as the error messaging for build failures.

Otherwise its very difficult to know how to fix NCrunch's build issues when Visual Studio, R#, and NUnit are not having any issues building the projects.
Back to top
Remco
#2 Posted : Wednesday, August 22, 2012 9:02:12 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,118

Thanks: 956 times
Was thanked: 1286 time(s) in 1193 post(s)
The issue you've described (no messages showing against build errors) is usually caused by an internal problem. I'd really like to learn more about this problem so that I can solve it properly. If you open up the Processing Queue Window and select the failed build in the list, is there any information showing in the text pane at the bottom of the window? If no information is available here, try going to your global NCrunch configuration and setting the log verbosity to 'Detailed', then resetting your engine. This should increase the amount of data shown in the processing queue output. If you can share the output with me, I can probably provide you with a workaround and also introduce a fix in an upcoming version.

The logic behind placing build errors in the Tests Window was to try and reduce the number of windows you would need to switch between in order to work with the engine. As such, you're absolutely right that the name 'Tests Window' probably isn't appropriate any more and perhaps this should be revised to something like 'Status Window'. The window itself is still an evolving concept and will likely see some huge change over the next couple of years.


Thanks!

Remco
Back to top
CreepyGnome
#3 Posted : Wednesday, August 22, 2012 9:46:15 PM(UTC)
Rank: Member

Groups: Registered
Joined: 8/21/2012(UTC)
Posts: 22
Location: Arizona

Thanks: 2 times
Was thanked: 5 time(s) in 5 post(s)
I didn't mention it in the original post, but I select Rebuild selected components from the NCrunch Tests window that it does take me to when I double click the NCrunch status icon it builds fine. So I would have to wait until it happens again to be able to open the Processing Queue window to look at it there. I will go set the log verbosity to detailed as well for the next time it happens. So this happens sometimes twice in a day or just once in a week. When it happens next I will post more information.

This process queue window would be the perfect window to take the user to and select the error in it when you double click the NCrunch status icon. Since it is a not a unit test that failed it is really not a good idea to take me to the unit test window here. The name of the window is correct, because the only ICONs in the toolbar are related to the running of and results of the tests. There is no rebuild selected component, or any other non-test related functions really in this window except for the right click of a project and not a test. You could also have two numbers in the status bar, one for Test Errors, and one for All other errors. Or if as you say the window is evolving then you would be overloading the test runner window with non-test runner stuff and that could make it a less favorable user experience depending on how it evolves.

I am also using Visual Studio Ultimate 2012 RTM release with NCrunch 1.41.0.50b.
Back to top
1 user thanked CreepyGnome for this useful post.
Remco on 8/23/2012(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.032 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download