GreenMoose
My feedback
44 results found
-
45 votes
-
2 votes
-
1 vote
-
1 vote
An error occurred while saving the comment -
1 vote
-
5 votes
-
1 vote
-
31 votes
-
2 votes
-
7 votes
An error occurred while saving the comment Regarding my comment about debugging tests: If you output via trace (e.g. by using TraceAppender for log4net) the output is shown "realtime" during the debug session.
An error occurred while saving the comment Also helps out a lot when debugging tests since then you can see log output etc. while you are debugging.
-
1 vote
-
1 vote
-
2 votes
-
2 votes
-
1 vote
-
2 votes
An error occurred while saving the comment @Matthew Steeples: No, as long as it is set as delayed start it works fine.
An error occurred while saving the comment For the record, if I do NOT use delayed start on Azure grid nodes they never can be connected to until I restart the grid node services so I guess having it default set as suggested here makes better sense than not having it set.
An error occurred while saving the comment FWIW , there is a feature request to keep options set in the service during upgrades:
https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5850101-remote-server-remember-service-settings-for-gridNot sure if everyone would like a delayed start by default but if service settings were persisted it would not be an issue.
-
3 votes
An error occurred while saving the comment An alternative to the "full blown specific project" thing might be If engine mode supported expanding of environment variables so one can set up 1 engine mode and then modify variable accordingly to get different engine behavior? (Given that it could be taken care of without restarting the NCrunch process, e.g. via WM_SETTINGCHANGE or similar).
Not as user friendly as original feature request but I guess effort to implement it might decrease significantly.
-
6 votes
An error occurred while saving the comment @Darius: I think it is even more common when having grid nodes so tests might fail on some nodes but not others, e.g. node isn't performant enough for specific tests, have incorrect test filters, can't reuse cached data etc. I would find it valuable be able to "post review" the reasons for failure. (Also NCrunch seems to sometime re-run a test yet again when pinning it, let it be bug or not, causing my red test I want to investigate to suddenly become green with the reason of previous failure is nowhere to be found).
-
4 votes
An error occurred while saving the comment Current workaround is rather simple it turned out, copy engine modes in a text editor for file *.v2.ncrunchsolution and then edit as needed in via UI.
-
1 vote
Same as this I think https://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5850101-remote-server-remember-service-settings-for-grid