The behat step "i_am_on_course_homepage_with_editing_mode_on" in behat_navigation.php is used many times throughout the code base.

However, checking that editing can be switched on via a button should only be tested once as it is slow.

For the rest of the time, the behat test should simply navigate directly to the appropriate url with edit=on as a parameter. This is much faster.

It's also important to note that there is already a step to simpy turn editing on so there is no need to write this code again or even test it again (i_turn_editing_mode_on in behat_course.php).

For optimal performance with behat testing there should be two types of step a) A UI test step where it actually clicks on stuff - this only needs to be implemented once as a test per feature b) A performant utility step that gets you to where you need to be as quickly as possible.