1 comment
Comment actions Permalink

When ReSharper runs Unit tests, it runs separate application.
The easiest way to debug it is to create dummy test in your plugin, and
debug it :)

What about row tests and "mangled" test names:
Personally, I do not see any problems to generate test names such as
"SomeMethod(1,2,3)"
and then during execute match this string with exact row test parameters

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Albert Weinert" <newsH2-06@der-albert.com> wrote in message
news:57z7pchq8ea7$.1nyqrd61n4ftx.dlg@40tude.net...

Hi,

>

i'm trying to write a Unit Test PlugIn for MbUnit ('cause JetBrains does
not write one).

>

So, i take Reflector and look inside the NUnit Unit Testing Assembly of
ReSharper.

>

I implemented a MbUnitCodeExplorer class (based on IUnitCodeExplorer) and
a
MbUnitTestAssembly class (based on UnitTestAssemblyBase, but not working).

>

MbUnitCodeExplorer was not so a big Problem, there a some differences for
MbUnit (More TestFixture-Attributes and more Test-Attributes) also that
the
Method for MbUnit can have parameters.

>

The Debugging of MbUnitCodeExplorer was pretty easy after the build i copy
the assembly to %APPDATA%JetBrains\ReSharper2\Plugins\MbUnit, also i have
Visual Studio as application for the start action, so that for debugging a
new instance of Visual Studio will be started. So i can step into the code
an debug it.

>

But with the MbUnitTestAssembly class which runs the test this seems not
possible. If i run a the Tests the MbUnitTestAssembly.Run() is called, but
no breakpoints do their job. And this is bad, i have some weird error and
cannot debug. How to debug?

>

Also only getting the names of the methods (in MbUnitTestAssembly.Run())
seems not enough information for MbUnit, cause MbUnit Test Methods can
have
parameters, and methods with the same name can have different parameters.

>

Regards

>

Albert
http://der-albert.com



0

Please sign in to leave a comment.