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

Notification

Icon
Error

Run Tests As Administrator
Rodney
#1 Posted : Friday, March 8, 2013 12:06:38 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/7/2012(UTC)
Posts: 17
Location: United States of America

Thanks: 1 times
Was thanked: 2 time(s) in 2 post(s)
It would be nice if on a project configuration setting if we could have a setting called "Run tests as Administrator" it could default to false. Then we can set it to true when needed.

This is a huge issue when developing on a box with UAC enabled. If you ask why in the heck would you develop on a box that has UAC enabled, the reason is we didn't used to but tons of elevation bugs stunk through that wouldn't have if the developers environments where UAC enabled. It also allows us to feel the pain typical users would feel using are applications as we dog food them.

So we as a practice run Visual Studio as a normal user and for everything it has been great until we started getting more into unit testing and a small number of the "mocks" and "mock environments" we need require elevated rights. So we have been creating the tests and marking them as explicit or ignored with NUnit attributes.

Then once in a great while we will launch VS as an Admin and then run them.

With this feature every run would trigger an elevation prompt but we could leave the as explicit so they don't run automatically but then we wouldn't have to launch a new VS as an admin just to run these few tests. They will get run more often by the dev's with this feature.

Remco
#2 Posted : Friday, March 8, 2013 2:17:46 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 959 times
Was thanked: 1290 time(s) in 1196 post(s)
Hi Rodney -

Thanks for the suggestion.

UAC is often a problem during development. NCrunch itself is developed on a system with UAC enabled for just this reason - stuff tends to go haywire unexpectedly when it hasn't been fully tested with the extra security constraints.

Unfortunately setting up a feature like this is immensely challenging because it makes the NCrunch runtime environment much more complex. Windows security is very configurable and this would give rise to far more unexpected environment-specific problems that would make this feature difficult to troubleshoot. I have to say that the time spent trying to perfect such a feature would far outweigh the benefits (for example, it would require less effort to make the engine run 20% faster). The need to click the elevation dialog would also mean that this feature couldn't be used for continuous testing (which is the primary purpose of NCrunch), making the feature somewhat out of the current development plan.


Cheers,

Remco
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.030 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download