Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Absent Member.. yogesh2602 Absent Member..
Absent Member..
1309 views

.net Thick Client Testing +Rabbit MQ Load Testing

Hi,

 

One of our application is a .net thick client and is using Rabbit MQ for sending messages between servers(Cloud based servers).

 

However i am not sure how can i work with Rabbit MQ and also only one insatnce of application can be opened at once.

 

Is it possible to do load testing using Load Runner.

 

Thanks in advance!!

0 Likes
4 Replies
A_Bondarenko Absent Member.
Absent Member.

Re: .net Thick Client Testing +Rabbit MQ Load Testing

Hello!

 

The overall complexity of this task depends on how good do you know the application and the RabbitMQ internals.

 

I don't see any problem in recording RabbitMQ-based client-server calls, but the built-in VuGen environment filtes would'n help a lot, because at a glance, RabbitMQ implements its own set of classes and interfaces for most of the work,

so including WCF filter is not a solution.

You will want to create a new custom recording filter, add the RabbitMQ.ServiceModel and RabbitMQ.Client DLLs to this filter, and include the corresponding interfaces in the filter. You will need to make some investigation on what to include, I couldn't help here because this framework is new for me.

 

Next, regarding single instance restriction. As soon as you are already using cloud in your solution, I can suggest you to try LG Cloud via MS Azure, it could do.

If the restriction is related to some internal thick client stuff, that would not affect the replay, then running several instances alongside should not cause any issues (because we suppose we extracted only pure RabbitMQ client-server interaction script), but only the way of trial and error would fork here, as for me.

 

Kind regards, Alexey Bondarenko

LR RnD, .Net protocol

 

 

Absent Member.. yogesh2602 Absent Member..
Absent Member..

Re: .net Thick Client Testing +Rabbit MQ Load Testing

Thanks for your help but i am new to LR and i have worked only on web protocol so far.

 

I have very little clue about this can you tell me how can i define these filters that you are talking about

 

also we dont have LG cloud ms AZURE, is it not possible using LR?

 

Also if possible can you any helpful link which i can refer

 

Thanks,

 

0 Likes
Highlighted
A_Bondarenko Absent Member.
Absent Member.

Re: .net Thick Client Testing +Rabbit MQ Load Testing

I recommend you to refer the VuGen help, section related to .Net protocol recording options. There you can learn how to manage the recording filters (filters are intended to specify which activity, classes, and methods to record).

First steps I'd take - is to create custom filter, add reference to RabbitMQ.Client and RabbitMQ.ServiceModel, include the very basic top-level interfaces in those dlls (like RabbitMQ.Client.IConnection, RabbitMQ.Client.IConnectionFactory) and the main classes that are responsible for client-server interaction. You have to refer RabbitMQ documentation here, I'm sorry I can't provide more info, because don't know much about this framework.

 

A_Bondarenko Absent Member.
Absent Member.

Re: .net Thick Client Testing +Rabbit MQ Load Testing

Here is the path where to find filter manager documentation in the VuGen help:

VuGen > VuGen > Script Workflow > Recording > Recording OptionsFilter Manager (.Net Protocol)

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.