citrus-simulator
citrus-simulator copied to clipboard
MessageHeader filter on Message REST resource
At my company, it's good practice to check whether a Message has arrived at the simulator with the right body. we do that right at the end of each test. in order to find the correct message, we filter them based on their tracing headers (MessageHeader).
So that we can delete our custom code - and because it seems like a fear feature for others - I think the functionality should be added to the Message REST resource. it can already filter results by MessageHeader, but just by its ID as of now.
that being said, it's fairly easy to implement - maybe a matter of an hour. all required code parts already exist, as well as an example (filter by ID). maybe two hours with docs. but I want to give others a chance to look into the simulator v3 code. that's why I would like not to implement it myself.
for the UI, it would basically result in another View "Simulations" alongside the "Scenarios".
mimicing the old "Activity" view with its filters: