Requested Option for Removing Unit Test Functionality

I placed a request in the Tracker for the ability, in Resharper 2.0 options, to disable the Unit Testing feature.

I asked for this for a couple reasons:

1) Short term, bugs are keeping from using the Unit Test ui in VS2003 or 2005. They are reported but as yet unaddressed. In both cases they are fairly essoteric and I'm not sure they will get addressed by production
(see http://www.intellij.net/tracker/resharper/viewSCR?publicId=14439 and
http://www.intellij.net/tracker/resharper/viewSCR?publicId=14174
)

2) Many people have established procedures for Unit Testing. In many of my projects, NUnit Project Files drive the Unit Tests and are included as artifacts of testing. Other people swear by the TestDriven.Net Add-In. Finally, Team System has it's own test abilities that projects will adopt.

I love Resharper and all it's features, but in this case I don't need it to spend cycles tracking Unit Tests and add more Menu Items to my already crowded menus.

I put in a request for an option to disable:

1) processing of the Unit Test files and icons in the gutter;

2) menu items.

Does anyone else see the need for this option?

Thanks - Jeff Odell

12 comments
Comment actions Permalink

I should have provided a link to the request in Tracker:

http://www.intellij.net/tracker/resharper/viewSCR?publicId=16320

In case you want to vote :>

0
Comment actions Permalink

Does anyone else see the need for this option?


For me this option is very convenient. Because TestDriven.NET don't work in
VSTS 2005 (unfortunately). And integrated Unit Test launching mechanism is
very unconvenient. For me, the only choice left is R# + NUnit. The only
disturbing thing is that links to the code of failed test don't work.

Regards,
Andrew Ovchinnikov


0
Comment actions Permalink

Hello Jeffrey,

option for not placing Unit Tests menu items (as well as disabling Unit Test
functionality) looks clumsy for me. Please
note that in VS you can customize menu items as you like it, adding and removing
items to any menu context menus
including. Since menu layout is persisted, this should be done only once.


Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I put in a request for an option to disable:

>

2) menu items.



0
Comment actions Permalink

TestDriven.Net has been updated to work with VSTS, albeit in beta form.

http://weblogs.asp.net/nunitaddin/archive/2006/01/25/436420.aspx

Andrew Ovchinnikov wrote:
>> Does anyone else see the need for this option?


For me this option is very convenient. Because TestDriven.NET don't work in
VSTS 2005 (unfortunately). And integrated Unit Test launching mechanism is
very unconvenient. For me, the only choice left is R# + NUnit. The only
disturbing thing is that links to the code of failed test don't work.

Regards,
Andrew Ovchinnikov

0
Comment actions Permalink


"Alex Hung" <ahung@xbsolutions.com> wrote in message
news:dr84qq$f0o$1@is.intellij.net...

TestDriven.Net has been updated to work with VSTS, albeit in beta form.

>

http://weblogs.asp.net/nunitaddin/archive/2006/01/25/436420.aspx


Yes, I know. But it doesn't work. I don't know why. I have even downloaded
the latest build, but it didn't help.
The issue is that, when I clich on "Run Tests", doesn't matter where. It
runs. But then it shows message in the status bar:
"0 Passed, 0 Failed, 0 Skipped".

Doesn't matter which test engine I use: NUnit or VSTS. That's why R# is the
only way for me to run tests.

Andrew


0
Comment actions Permalink

Hello Andrew,

and why do you need an option to disable Unit Test functionality in R# then,
I wonder?
You mentioned in you previous post that such an option would be convenient.

Regards,
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Alex Hung" <ahung@xbsoluti> Doesn't matter which test engine I use: NUnit

or VSTS. That's why R#

is the only way for me to run tests.

Andrew



0
Comment actions Permalink

and why do you need an option to disable Unit Test functionality in R#
then, I wonder? You mentioned in you previous post that such an option
would be convenient.


Hm. Seems some misunderstanding, sorry.Wrote previous post in the evening,
very tired and missed "option". I thought, that request was to disable unit
testing capability at all, that sounded strange for me.

Probably need to read newsgroups in the morning :))

Andrew


0
Comment actions Permalink

For me, the only choice left is R# +
NUnit. The only disturbing thing is that links to the code of failed
test don't work.


What do you mean?

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> Does anyone else see the need for this option?
>>

For me this option is very convenient. Because TestDriven.NET don't
work in VSTS 2005 (unfortunately). And integrated Unit Test launching
mechanism is very unconvenient. For me, the only choice left is R# +
NUnit. The only disturbing thing is that links to the code of failed
test don't work.

Regards,
Andrew Ovchinnikov



0
Comment actions Permalink

Hello Valentin,

What do you mean?

I saw several times when cilcking on a link does not navigate to the corresponding
source file. Unfortunately, I do not know any repro for this.

More serious problem is that stack explorer does not resolve some locations:
1) locations for explicit interface implementations (this bug is there since
1.0)
2) locations in generic classses

Do you have any plans for fixing it?

Best regards,
Maxim



0
Comment actions Permalink

Yes, this is true, but I don't really need the icons in the gutter and associated processing.

At the end of the day, I guess I feel like I needed Resharper to do refactoring and not Unit Testing as I have viable and established (and free) tools for Unit Testing. Since the Unit Testing features do not yet work for me in most cases, it is more of a nusiance that a help at this point.

If the bugs clear up and Unit Testing begins to work I may switch to using Resharper's Unit Testing tools. I am a user of dotTrace and if the Unit Testing dialog connects properly to dotTrace, that is more compelling.

0
Comment actions Permalink

1) locations for explicit interface implementations (this bug is there
since
1.0)
2) locations in generic classses


Both bugs will be fixed in 2.0.

Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Valentin,

>> What do you mean?
>>

I saw several times when cilcking on a link does not navigate to the
corresponding source file. Unfortunately, I do not know any repro for
this.

More serious problem is that stack explorer does not resolve some
locations:
1) locations for explicit interface implementations (this bug is there
since
1.0)
2) locations in generic classses
Do you have any plans for fixing it?

Best regards,
Maxim



0
Comment actions Permalink

Hello Valentin,

>> 1) locations for explicit interface implementations (this bug is
>> there
>> since
>> 1.0)
>> 2) locations in generic classses

Both bugs will be fixed in 2.0.

Thanks!

Best regards,
Maxim



0

Please sign in to leave a comment.