-
Notifications
You must be signed in to change notification settings - Fork 94
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
analytics - fixing filtering by roles #2698
Conversation
analytics/pom.xml
Outdated
@@ -1,599 +1,704 @@ | |||
<?xml version="1.0"?> |
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 did not expect such a reindentation on the pom, sorry about that. Maybe we shall stick with 2 spaces on xml files ?
When merged, this will require to merge 18.06 into 19.04 into master ... |
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.
Looks good overall. Please check this branch for some fixes/improvements: https://github.com/groldan/georchestra/tree/pmauduit-it-analytics-2685
Had to test it out thoroughly to catch those hence the commits instead of just comments.
It'd be good if you can squash all commits in the PR into a single one and provide a descriptive commit message of what it encompasses functionality wise.
The correct command would then be:
You'll get a number of files deleted in 19.04, so do:
And select the |
Since the group -> role renaming in georchestra, this feature (being able to filter by roles via a parameter) has been probably broken. This also adds an integration test to validate the current fix.
d15ee81
to
7ee9532
Compare
Done |
private static boolean dataLoaded = false; | ||
|
||
public @Before void before() throws Exception { | ||
if (!dataLoaded) { |
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 think @groldan provided a better approach while working on GPDR:
https://github.com/georchestra/georchestra/pull/2613/files#diff-0cdf168c2c66425c514a83589eeddd9dR62
The annotation comes from com.github.database.rider and should do the work better than I can do in this before() method
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.
IIUC, you do not consider this one is ready for merge ?
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 was wondering if it was worth to integrate this database-rider dependency (on a test scope) or not. In the current state, it works, it would be fancier with it.
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 did some rapid tests with database-rider (the DataSet
annotation), as well as the Sql
from spring-tests, but with no luck, I cannot get them work to load my fixtures.
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.
trying harder I succeeded \o/ I'll update my PR actually
See #2685 ;
Note: this PR introduces some integration tests on the analytics webapp, inspired from the ones introduced in 19.04 for the console, but:
Tests:
mvn test
okmvn verify -Pit
okCredits goes to @groldan for the help !