-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add minimal coverage for local Infinispan and for working with DevMode #984
Conversation
4855a27
to
ec4a0e4
Compare
nosql-db/infinispan/src/test/java/io/quarkus/ts/infinispan/InfinispanIT.java
Outdated
Show resolved
Hide resolved
import javax.ws.rs.Path; | ||
|
||
@Path("/first-counter") | ||
public class FirstCounterResource extends InfinispanCounterResource { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure if this class is required or if we can just move the Path definition to InfinispanCounterResource
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was copied from the infinispan-client
module, so I may be wrong, but I presume this is required to guarantee, that we are addressing different beans
ec4a0e4
to
c85cea6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just minor cosmetic change :(
c85cea6
to
d39e523
Compare
d39e523
to
7c2ed5b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary
Adds coverage for a bug, encountered in https://issues.redhat.com/browse/QUARKUS-2747.
The separate module was created, since
application.properties
files for this scenario and for scenarios ininfinispan
module are not compatible and we cannot customise them with per-app granularity, because of quarkus-qe/quarkus-test-framework#174.The module has as little coverage as possible to minimise running time and consumed resources.
Please select the relevant options.
run tests
phrase in comment)Checklist: