Closed nikkimk closed 1 month ago
Category | Latest (report) | Main (report) | Branch (report) |
---|---|---|---|
Performance | 0.99 | 0.99 | 0.99 |
Accessibility | 1 | 1 | 1 |
Best Practices | 1 | 1 | 1 |
SEO | 1 | 0.92 | 0.92 |
PWA | 1 | 1 | 1 |
main
("Main"). Higher scores are better, but *note that the SEO scores on Netlify URLs are artifically constrained to 0.92.*
Category | Latest | Main | Branch |
---|---|---|---|
Total | 222.54 kB | 210.768 kB 🏆 | 211.012 kB |
Scripts | 54.598 kB | 48.307 kB 🏆 | 48.592 kB |
Stylesheet | 35.098 kB | 30.553 kB | 30.522 kB 🏆 |
Document | 5.997 kB | 5.285 kB | 5.275 kB 🏆 |
Font | 126.847 kB | 126.623 kB | 126.623 kB |
Category | Latest | Main | Branch |
---|---|---|---|
Total | 45 | 45 | 45 |
Scripts | 37 | 37 | 37 |
Stylesheet | 5 | 5 | 5 |
Document | 1 | 1 | 1 |
Font | 2 | 2 | 2 |
@nikkimk Tests are making some noise! Can you please check and do the needful so that we can land this!
- (Note: There is no way to use
SendKeys
to test Numpad keys)
@ blunteshwar any ideas on how to add tests for this given the above?
- (Note: There is no way to use
SendKeys
to test Numpad keys)@ blunteshwar any ideas on how to add tests for this given the above?
I think you can use SendKeys to send Numpad keys await sendKeys({press: 'NumpadEnter',});
will work just fine.
I am attaching a videos as well where it is shown that replacing Enter
with NumpadEnter
has no effect on tests.
We can write a test for 'Enter' and 'NumpadEnter', i think a single test with enter key can verify the changes.
@blunteshwar thanks. I've added the update. We just won't be able to do Numpad arrow keys that way.
Description
Handles
keydown
event byevent.key
instead ofevent.code
so that numpad keys will work with menu.Related issue(s)
How has this been tested?
Types of changes
Checklist
SendKeys
to test Numpad keys)