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
#83 Have performance tests #119
#83 Have performance tests #119
Conversation
Hi, thanks for the contribution, and sorry for taking that long to look at it. Could you add a short README which instructs on how this should be used? (It is not part of the normal Travis CI build, right?) Then @BGehrels and me can test this based on the README. |
|
||
usage: | ||
``` | ||
mvn test -Dtest=LoadTestIT -Dgpg.skip=true |
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.
so, one should probably run docker-compose up before?
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.
The documentation was enhanced to clarify this topic.
👍 |
Tested it, looks great. |
@ePaul What do you think? I would love to get this merged |
👍 |
Looks fine. I wonder whether we want to run this on Travis for feature branches, just to have a record of how the execution time changed. Though this will also depend on the used hardware. In any case, that would be a separate PR, not part of this one. Thanks for the contribution, and sorry for taking that long to merge it. |
#83 Have performance tests