Looking at the demo page, material-ui – switches

• right-click on one of the switches
• select “inspect”
• in the elements pane, right-click the input and select “Store as global variable”
• in the console pane, shows “temp1”
• enter “temp1.click()”
• it changes!

Saves all the guess-work!

So, on that page to target the second toggle,

cy.get('span.MuiSwitch-root')
  .eq(1)
  .find('input')
  .click();

Note: It’s a toggle so click() will go from on to off and from off to on.

Each test should be written such that you know the state of the form. The idea of conditional testing is not good – I mean, when you navigate to the page you don’t get a random toggle state. Most likely it starts off with the form hidden.

You tests would be

• when the page opens, test that the form is hidden
• when the user clicks the toggle, test that the form becomes unhidden

etc.