-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
refactor(TestChartApi): move chart data api tests into TestChartDataApi #17407
refactor(TestChartApi): move chart data api tests into TestChartDataApi #17407
Conversation
Codecov Report
@@ Coverage Diff @@
## master #17407 +/- ##
==========================================
+ Coverage 76.97% 77.04% +0.07%
==========================================
Files 1041 1041
Lines 56069 56063 -6
Branches 7742 7738 -4
==========================================
+ Hits 43157 43194 +37
+ Misses 12654 12611 -43
Partials 258 258
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Thanks for the contribution! @ofekisr Looping domain experts in to review your PR. since it's an XXL one with high risk, we may take awhile to get through the review. Please stay tuned. |
41d47ab
to
1358e71
Compare
I sync the branch from master so now it contains only 3 files |
@ofekisr could you list the product area that will be affected by your PR, and do a simple audit what's the test coverage look like in those area? |
Product area is not affected bc no code changes to the product only to tests |
# Conflicts: # tests/integration_tests/charts/api_tests.py
mapping from the old test name (chartApiTest) to the new name in ChartDataApiTest test_chart_data_simple --> test_with_valid_qc__data_is_returned |
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.
Reviewed that entire 2 suites of tests move and renaming and all test remain as the original.
Some boiler plate code was moved to setup
LGTM!
This was a nice improvement and provides for a much better chart API development experience! |
…pi (#17407) * refactor charts api tests * move new added test * refactor charts api tests
Background
When we have worked on #16991 we wanted to test the new functionalities in concrete and accurate unittest.
All chartData flows and its components are too couple to superset so it is impossible to create unittests.
The flows are not testable and so many components do not meet the very important principle SRP and the code became so dirty
So I've started to refactor it (#17344 ) but many changes were added and it was hard to review so I decided to split those changes into small PRs so will be easier to follow
This is the fourth PR in a sequence of PRs to meet these
The Next PR is #17425
PR description
In #17400, ChartData endpoints were moved to a new view, so the tests should move too.
What else?
Test plans
should we test the tests? :)
Previous PRs