Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JmsListenerTest and JmsListenerTestHarness similar to spring-amqp 1.6 and spring-kafka [SPR-14073] #18645

Closed
spring-issuemaster opened this issue Mar 21, 2016 · 1 comment

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Mar 21, 2016

Bartolom opened SPR-14073 and commented

The Spring-Integration team recently annonced spring-amqp 1.6.0 Milestone and a spring-kafka milestone

https://spring.io/blog/2016/02/16/spring-amqp-1-6-0-milestone-1-and-1-5-4-available
https://spring.io/blog/2016/03/14/spring-for-apache-kafka-milestone-1-available

Both contain a new testing feature
http://docs.spring.io/spring-amqp/docs/1.6.0.M1/reference/html/_reference.html#testing
It leverages Mockito, which I think is also the main mocking library in Spring-Framework

In essence it is possible to intercept @RabbitListeners and inject CountDownLatches or arbitrary lambdas that can be controlled by a test method.

We see value in these kind of test setup and it would be nice when spring-jms would support it too.

Our use case is something like that: We don't have an application where the Web-GUI is the most important part but we rather process invoices (Apache Camel, a bit Spring-Integration). We have automated "Acceptance Tests". We are slowly moving to a more distributed setup where we have new/someExisting parts (re)written in Spring Boot and they integrate via a JMS-Broker.

It becomes now harder to write the automated "acceptance Tests" and any additional support by the framework where we can inject CountDownLatches or lambda functions would be appreciated.

For instance 1 invoice comes in and gets split up into 5 of which one fails and shound end up in queue X but the other 4 should procced to the next queue and picked up by the next Spring Boot app.


Affects: 4.2.5

1 votes, 3 watchers

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Jan 12, 2019

Bulk closing outdated, unresolved issues. Please, reopen if still relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.