Non-blocking: I'm somewhat worried about all of the test logic getting stuffed intoverifyConfigFlag. Any other special cases will also need to get stuffed in there.

I wonder if we could instead refactorverifyConfigFlag to accept a function that takes a function as an argument. This function should just run whatever assertions are necessary for the particular config flag.

Then the responsibility for asserting the content of the node moves back up to the test instead of in this function, e.g.

  verifyConfigFlag(page, config, flag, (configOpt) -> { expect(configOpt.locator(`...`)).toBeVisible()  })

andverifyConfigFlag is just concerned with finding the relevant option on the page and passing it to the function.

WDYT?