Bug 1539232 - Switch Perfherder to react-router#5379
Conversation
a189ae7 to
cf197ac
Compare
|
@camd There's a selenium test that's failing - this test for switching between Treeherder and Perfherder in the dropdown menu. Do you think this is worth trying to get working or were you planning to rewrite at some point? I've rewritten the other tests for Perfherder using react-testing-library so this is the only remnant of Perfherder selenium tests. |
cf197ac to
62cff4f
Compare
Codecov Report
@@ Coverage Diff @@
## master #5379 +/- ##
==========================================
+ Coverage 36.94% 37.01% +0.06%
==========================================
Files 190 190
Lines 5995 6001 +6
Branches 1331 1341 +10
==========================================
+ Hits 2215 2221 +6
- Misses 3490 3491 +1
+ Partials 290 289 -1
Continue to review full report at Codecov.
|
Cameron's #5383 pr fixed this problem. |
|
I only managed to see that the permalinks from the Compare view no longer work as expected. STR
Expected: What we actually get: |
|
@alexandru-io @bebef1987 could you help me out on testing this PR next Monday? |
Ah, I know why it's doing that. It's because of how the top menu navigation is overlapping the view. So the permalink is still working correctly, I'll just need to fix how the menu is displayed. |
camd
left a comment
There was a problem hiding this comment.
Looks great! Wow, you're done! :) Nice work. Take the weekend off...
I didn't test this myself, I must admit. I'll trust to your testing here.
|
I am now resuming the testing on this PR. |
|
Bug #2 STR
Expected results: What we actually get: This bug is specific to this PR. |
|
Bug #4 STR
Expected results: What we actually get: |
|
Bug #5 STR Expected results: What we actually get: Note: this is a preexisting bug, which I've found just now. |
|
Bug #6 STR
Expected results: What we actually get: |
|
Login issue on Firefox and Chrome; STR
Expected results: What we get instead: Video with the issue from Alex: https://mozilla.zoom.us/recording/play/g5UjN_GDTxhejx0bepu3XyRSFa94S4_-wqFQyY652kSrTXPwMeqzHTgwp0ke4c7T?continueMode=true |
This is a false alarm. You were missing the |
Ok, interesting, thanks for catching it - that's been fixed. Why would you click on alerts twice though? |
|
@ionutgoldan Btw, when you write |
|
Thanks for the feedback @ionutgoldan - I'll continue working on these fixes tomorrow and give it a good last test before merging. |
Ok. Will use a different notation from now on. Thanks! |
|
Bug # 8 STR
Expected results: What we actually get: |
I don't see this as a bug per say - technically it is the the one and only page. However, if you would like to improve upon the pagination please feel free. |
Let's file any pre-existing bugs in bugzilla and not block this patch on them. |
Thanks for reporting this but it doesn't have anything to do with this pr, which is for testing react router changes on prototype. Please file a bug with the video. I was able to reproduce this once - following the sequence from your video - but then wasn't able to reproduce it again. This might be an edge case. Edit: I've been able to reproduce it again and will file a bug for it to save time. |
Use top-level of app as a cache for projects, frameworks, alerts data and compare data Cleanup files and move constants to dedicated perfherder file Remove angular-related libraries and bump up the neutrino entry and asset limits
62cff4f to
96a58c0
Compare
Will do. |
|
@sarah-clements @camd Congrats on finishing the AngularJS migration! :-) |
|
Thanks, @edmorley ! Great to hear from you! I hope you're well, old friend. :) |
|
Yes, @edmorley, it was a lot of work converting Perfherder and I'm glad it's finished! You should pop in the irc channel some time before it goes away... :) |
This is the final react conversion pr - woohoo!
In addition to setting up the routes, I've made these other changes:
@ionutgoldan it'd be worth you giving all the views a quick test. I unfortunately had a lot of squashing of commits to do during the rebase and I want to make sure the new retrigger action is working as expected. I'd also like to ensure that the fetched data that's stored from the alerts view (when navigating back from an individual alert), and the fetched data that's stored from the compare view (when navigating back from the comparesubtest view) works as expected and doesn't cause any issues. I've launched it to prototype.
FYI @karlht and @davehunt