eiffel-community / eiffel-community/eiffel-intelligence
Investigate if it is possible to verify if Eiffel messages has been sent in test.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently in flow tests and some other tests and integration tests the test will loop though a number of Eiffel events and throw them on RabbitMQ. This sometimes cause events to be lost since either RabbitMQ or Eiffel Intelligence cannot handle the load. This makes test fail.
This issue is about investigating if it is possible to get acknowledgement from RabbitMQ that an event has successfully been sent to the message buss, and then recieved and and processed by Eiffel Intelligence.
If implementation is simple do the implementation, but if the implementation is complex, create a new issue.
We have currently implementet a simple delay in Eiffel Intelligence Artifact flow integration test as a work around for this issue.
Motivation
Improve stability in tests.
Exemplification
Send an event, verify that event has been recieved my RabbitMQ, send next event. Ensure all tests passes in Linux, Windows and Travis. Rerun test at least 10 times.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Eiffel Intelligence Artifact flow integration test and its current delay workaround. Investigate whether RabbitMQ acknowledgements and Eiffel Intelligence processing can be observed before sending the next event. Done means the tests avoid lost events, pass on Linux, Windows, and Travis, and succeed across at least 10 reruns; document a follow-up issue if implementation is complex.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rabbitmq
- Domain
- backend, distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100