citrus
citrus copied to clipboard
Framework for automated integration tests with focus on messaging integration
**User story** As a citrus newbie, I would prefer the logs to say things like "**Awaiting** JMS message on destination...." or "**Awaiting** message from ..." instead of "Receiving JMS message...
**User story** As a citrus newbie, I would like to pass an enum value (not a string) to `ExecuteSQLQueryBuilder#validateScript()` to define script type, so that I don't have to look...
**User story** As a citrus user, I would like to be able to chain `ExecuteSQLQueryBuilder#validateScript` calls to add multiple validation scripts, so that each script (and resulting error message) is...
**Citrus Version** tested with 2.7.6 **Expected behavior** Calling purgeEndpoints with an endpoint that was not used to send messages has the same behaviour as calling the method with an endpoint...
**User story** As a citrus test developer, I want to be able to wait for a certain payload from my microservice http endpoint, to evaluate whether the service is ready...
**User story** As a citrus newbie, I would love to see a self-explaining method for adding selectors e.g. to `HttpServerRequestActionBuilder`, so that I know how to use selectors without reading...
**Citrus Version** 2.7.6 **Expected behavior** `repeatOnError().until(true).action(errorThrowingAction)` should execute `errorThrowingAction` exactly once, causing the test to fail **Actual behavior** `errorThrowingAction` is not executed (because the repeat-until condition is evaluated first), causing...
**User story** As a software developer, I would love to see a convenient way to configure retry count of `repeatOnError`, so that I can write citrus test even faster. Currently...
**User story** As a software developer, I would like to have one or more examples in the JavaDoc of `RepeatOnErrorBuilder#until(String)` in order to be able to understand the expected condition...
**User story** As a citrus test developer, I want parallel http send actions to be mapped automatically to their receive actions so that I don't have to map them manually....