Adding cypress tests for hotkeys

[gikf]

Issue for tracking adding cypress tests of hotkeys, as per #42503.

Challenges / Projects / Video challenges:

• Navigation mode - 'escape'
• Previous challenge - 'p'
• Next challenge - 'n'
• Focus on editor - 'e'
• Focus on instructions panel - 'r'
• Running the tests - 'ctrl + enter' / 'command + enter'

[Sembauke]

Hey @gikfk, Are you still planning on working on this?

[gikf]

Hey @Sembauke, sorry, I haven't managed to start on this yet. If you'd want feel free to have a go at it.

[lastrafda]

I would like to work on this @Sembauke

[Sembauke]

Hey @lastrafda,
This is a pretty though one, let me know if you need some help.

[lastrafda]

Thanks @Sembauke I'll let you know! In fact I do need some help
I was looking at a video challenge and I realized that you have to click inside the main tag or focus the "Check your answer" button in order to be able to use the previous challenge and next challenge hotkeys, is this the expected behavior?

[ShaunSHamilton]

@lastrafda

you have to click inside the main tag or focus the "Check your answer" button in order to be able to use the previous challenge and next challenge hotkeys

Expected behaviour is using the esc key to allow the hotkeys to be targeted. That is, to enter navigation mode:

Navigation mode - 'escape'

[Sembauke]

I've tested some of the hotkeys and the previous and next challenge hotkey does not seem to work for me. Can anyone test this out?

[gikf]

Any specific challenge type?

• classic challenges: esc ->p and n works for current and challenges that are changed to
• backend/project challenges: esc -> p and n works for current and challenges that are changed to
• video challenges: click on page -> esc -> p and n works for current challenge, after changing challenge with hotkey, it's needed to click again on page to be able to use p or n

[ojeytonwilliams]

video challenges: click on page -> esc -> p and n works for current challenge, after changing challenge with hotkey, it's needed to click again on page to be able to use p or n

Good catch @gikf I'll add a fix to Sem's PR.