-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
[Enterprise Fee Summary] Merge "Enterprise Fee Summary" report to master #3415
Conversation
@kirstenalarsen Were you able to test #3115 with the recommendations I made in the issue description before? I was the one who merged that PR in the transitional branch, so I included an updated version of that (I added Items 2 and 5) here for a more thorough round of testing by a non-dev, before everything is merged to master. |
I moved this PR straight to "Test Ready" because these changes have already been approved in code review. |
@kristinalim I cannot stage this because the Semaphore build has failed . . |
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 pull request is too big to review thoroughly. But we reviewed all the individual parts. So it should be fine.
I'm really surprised by the huge amount of code for one report. Why do you think this report needs so much more code than others? Is it the nature of the complicated data structures?
@mkllnk I was surprised too, actually - I expected a lot of lines but not this much. Although it makes sense:
Looking at the line count, almost half of added lines are for new test files: $ wc -l $(find . -path "./spec/validators/*" -or -path "./engines/order_management/spec/*" -or -path ./spec/features/admin/reports/enterprise_fee_summaries_spec.rb -or -path spec/controllers/spree/admin/reports/enterprise_fee_summaries_controller_spec.rb)
[...]
1491 total |
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 the question would be: do you see how would you do this in multiple PRs that could go live individually? I think we need to learn to do that as a team.
Otherwise 👏 specially for your very high tests/code ratio
sooo. I am going to say that this is ok to merge to master as it is restricted to superadmin and it passes the tests above and doesn't break anything I have found a few issues where I'm not sure what it's doing - BUT I think we are going to be so much better off to look at this with real data . . so let's get it through! |
Merge to master as passes tests above and is restricted to superadmin There are some confusions, that I think need testing with real data |
|
Bad luck. EDIT doesn't fail when executed multiple times on my machine |
maybe rebase to get latest "flaky fixes"? |
The product import spec failure is also an "intermittent" failure, which has been fixed here: #3430. "Intermittent" because it will pass in less than 24 hours, when it's February 10 in Melbourne time. The other two are related to spec failures that still have open issues, but yes, better luck with a rebase. I don't have Github permissions to modify this upstream branch though. Asking on Slack for anyone (any of you) to do this, or give me enough Github permissions. 🙂 Thanks! |
Example usage: validates :start_at, date_time_string: true
Example usage: validates :related_post_ids, integer_array: true
The preferred language could change dynamically.
We should not presume what is not default for an enterprise fee object.
Make these follow the "#{SINGULAR_OBJECT}_factory.rb" convention.
Add test for more complex scenario where there is a coordinator and distributor fee for an incoming exchange, and a producer and coordinator fee for an outgoing exchange.
3200492
to
b6be8c4
Compare
Yes! 😁 A green build. Thanks for rebasing, @luisramos0! |
So this is ready to merge I think. Yay |
Putting the merge on hold until we get #3337 conflicts fixed. |
are we merging #3337 into this one and merging this one into master without staging/testing this and 3337 together? |
@luisramos0 That confused me too, because the base branch and separation of PRs is highly dependent on the timeline... How about we merge this tested PR into master first. Then for #3337, I will change the PR base branch of #3337 to |
@kristinalim you will know what's the best approach :-) |
If that doesn't horrify the merger, that's the approach that I think is efficient and is still safe. 🙂 👍 I will update the other PR as soon as this is merged. |
What? Why?
This would merge the transitional branch for the Enterprise Fee Summary to master.
What should we test?
a. Link in the admin Reports page
b. Filters are working
c. CSV report is working
d. HTML report (below filters) is working
Release notes
Changelog Category: Added
Discourse thread
Dependencies