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 PasynkovDeveloperJetBrains, Inchttp://www.jetbrains.com"Develop with pleasure!""Albert Weinert" <newsH2email@example.com> wrote in message news:firstname.lastname@example.org...
i'm trying to write a Unit Test PlugIn for MbUnit ('cause JetBrains doesnot write one).
So, i take Reflector and look inside the NUnit Unit Testing Assembly ofReSharper.
I implemented a MbUnitCodeExplorer class (based on IUnitCodeExplorer) and aMbUnitTestAssembly class (based on UnitTestAssemblyBase, but not working).
MbUnitCodeExplorer was not so a big Problem, there a some differences forMbUnit (More TestFixture-Attributes and more Test-Attributes) also that theMethod for MbUnit can have parameters.
The Debugging of MbUnitCodeExplorer was pretty easy after the build i copythe assembly to %APPDATA%JetBrains\ReSharper2\Plugins\MbUnit, also i haveVisual Studio as application for the start action, so that for debugging anew instance of Visual Studio will be started. So i can step into the codean debug it.
But with the MbUnitTestAssembly class which runs the test this seems notpossible. If i run a the Tests the MbUnitTestAssembly.Run() is called, butno breakpoints do their job. And this is bad, i have some weird error andcannot 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 haveparameters, and methods with the same name can have different parameters.
Please sign in to leave a comment.