How can we test an ETA consumer application

didier.nadeau

Hi,

I would like to know if there is a way (testing feed or application) to verify we properly handle various use-case in our ETA consumer application. More specifically, some use case that might happen when a stream stops working with an RSSL_MC_STATUS.

I have read https://community.developers.refinitiv.com/questions/7417/how-can-we-test-the-ema-consumer-application.html, however I would like to know if the situation has changed in the 2 years since. The solution proposed seems to be aimed at performance monitoring rather than testing if the application handle various problematic situations correctly.

For instance, we once receive an stream closed when a instrument was delisted, and this was not something we previously tested.

Is there a way to test an ETA consumer application ?

Thank you,

Didier

umer.nalla

Hello @didier.nadeau

In addition to Zoya's comments, the following may also be useful - depending on what kind of testing you had in mind:

Do you have an onsite TREP infrastructure or is it a managed / hosted scenario?

If you have an onsite TREP, then you can ask your Market Data admin team if they can help you test your app by trying some or all of the following:

•ADS process stop and restart whilst your app is running
•ADS process stop and then start your app.

•Stop individual service in ADSMON/ADHMON whilst your app running

•Stop individual service in ADSMON/ADHMON and then start your app

•Drop individual RICs in ADSMON/ADHMON whilst your app running.

•Change permissions in DACS to deny for some required RICs before starting of your app
•Change permissions in DACS to deny for previously permissioned RICs whilst your app is already running and successfully consuming some of those RICs

If you are unable to perform the above, then you can still take the Provider examples source code and modify it to mimic some of the above scenarios and then connect your consumer to the provider directly.

zoya faberov

Hello @didier.nadeau,

The way I would approach this in a production application design, is to start with ETA Developers Guide, either C++ or Java, Appendix A, "Item and Group State Decision Table". The table reviews the implemented permutations of Stream State and Data State. We make sure that our application is handling all of these conditions in a logical way and according with your error reporting requirements.