Regression testing

Please don't take this the wrong way, but do you guys regression test? How
will you ever get out of beta of every new release offers its own slew of
bugs?

J


4 comments
Comment actions Permalink

Please don't take this the wrong way, but do you guys regression test?


If you mean automated tests, yes, we do them.

How will you ever get out of beta of every new release offers its own
slew of bugs?


What exactly do you mean?

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

Please don't take this the wrong way, but do you guys regression test?
How will you ever get out of beta of every new release offers its own
slew of bugs?

J



0
Comment actions Permalink

I have to agree. I had my fingers crossed for 232, but the first time I hit
Enter the CPU went to 100 and stayed there. Other persistent issues for me
are:

- Incredibly slow (5-7 minutes) VS startup. My solution has 28 projects.
Without R#, it opens in about 30s to 60s.
- Background startup progress bar floats on top of my right-docked
tool-window tabs.
- Crashes with CPU at 100% on hitting enter in C# code file.
- On startup I get SQL Server error messages saying that database doesn't
have the required objects for diagramming! Weird. Why oh why should R#
trigger this?

IMHO, R#2 is suffering from feature bloat. For example, why the unit test
stuff? I can't speak for anyone else but I ain't going to switch from TD.NET
anytime soon. I would of been so happy with 1.5 on 2005.


"Jeff M" <jmichelson@unitec-corp.com> wrote in message
news:e0uuda$fo3$1@is.intellij.net...

Please don't take this the wrong way, but do you guys regression test?
How will you ever get out of beta of every new release offers its own slew
of bugs?

>

J



0
Comment actions Permalink

Hello Andrew,

please see my answers inline.


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

I have to agree. I had my fingers crossed for 232, but the first time
I hit Enter the CPU went to 100 and stayed there. Other persistent
issues for me are:

- Incredibly slow (5-7 minutes) VS startup. My solution has 28
projects.
Without R#, it opens in about 30s to 60s.


Have you got any non-C# projects in your solution?

- Background startup progress bar floats on top of my right-docked
tool-window tabs.
- Crashes with CPU at 100% on hitting enter in C# code file.


Does it happen always?

- On startup I get SQL Server error messages saying that database
doesn't
have the required objects for diagramming! Weird. Why oh why should R#
trigger this?


This is a known problem that ReSharper sometimes cause connections with remote
servers to establish
and other similar issues. We'll fix it soon.

IMHO, R#2 is suffering from feature bloat. For example, why the unit
test stuff? I can't speak for anyone else but I ain't going to switch
from TD.NET anytime soon. I would of been so happy with 1.5 on 2005.

"Jeff M" <jmichelson@unitec-corp.com> wrote in message
news:e0uuda$fo3$1@is.intellij.net...

>> Please don't take this the wrong way, but do you guys regression
>> test? How will you ever get out of beta of every new release offers
>> its own slew of bugs?
>>
>> J
>>


0
Comment actions Permalink

Have you got any non-C# projects in your solution?


Yes. Database and SQL Server Database Assembly.

Does it happen always?


No. I've managed to go 10 mins without it before.

This is a known problem that ReSharper sometimes cause connections with
remote servers to establish and other similar issues. We'll fix it soon.


Joy!


0

Please sign in to leave a comment.