Ranorex Forum

Hi,

We are currently evaluating Ranorex with a view to possibly replacing our current automation solution (Borland Silktest).

I was wondering if it is possible to integrate Ranorex into VS in the same way as Silktest ie adding a menu item to the VS toolbar from where you can create and run ranorex tests?

Please see attached screenshot.


[attachment]VS.gif[/attachment]


Thanks

Currently Ranorex does not provide a plugin for Visual Studio. You can implement Ranorex libraries in a project, but there is not direct integration of Ranorex Studio into Visual Studio.

I have requested a couple of times that they port the Ranorex Studio system to Visual Studio as a plugin. At this time it does not seem likely to happen.

That's a shame.

But you can already use VS to create and run Ranorex tests... You just don't have the nice little toolbar. Don't let a little thing like a toolbar item make your choice for you. Ranorex is so much more powerful and quite capable in VS. I do 100% of my automation through VS and am able to reap the benefits of getting to use a real language to code in and the usage of the full .NET framework.

Ciege,

While I agree that the Ranorex Libraries are very powerful in their own right, Ranorex Studio is so much more than a "nice little toolbar" that goes along with it.

Being a developer who writes tests, I understand and do utilize a lot of the behind-the-scenes features, but I also work with those who are used to manual testing and do not have the background you and I do in coding and creating the back-end.

RX Studio allows them to manipulate test cases, modules and repository objects in a way that is easy to understand and allows me an easier time maintaining things. The repository is central to this. I know you create all your objects at run-time through RXPath, so you don't find it as helpful, but for us it allows other people to get in and change things without having to know how to code. On top of that there is the Test Suite which is as close to drag-and-drop test automation as you can get, if the modules are created correctly.

Having this all be a part of VS would allow those that are in a pure VS environment to have an easier time moving between tools/projects.

krstcs wrote:Ciege,

Having this all be a part of VS would allow those that are in a pure VS environment to have an easier time moving between tools/projects.

Which is the situation we are in.

Thanks for your replies.

IKT