title: Test Cafe Headless Visibility Check
body: <p>When running in headless mode, should the tests make visibilty checks? When I run tests in normal chrome or firefox they all pass, but in headless mode I keep getting this error: </p>
  
  <pre><code>test('Assert navigation from Home to page x...', async t =&gt; {
  await t
      .expect(link.textContent).eql('page x')
      .click(link)
      .expect(getPageUrl()).contains('pagex')
  });
  
  Error: The element that matches the specified selector is not visible.
  </code></pre>
  
  <p>and when I add expect([someSelector].visibile).ok() I get this error:</p>
  
  <pre><code>   AssertionError: expected false to be truthy
  </code></pre>
  
  <p>I feel my approach to writing these tests for the specific prupose of running them in headless mode is incorrect. I'm not sure if running in headless mode impacts the overall approach to how tests are structured?</p>
  
  <p>I'm writing a number of e2e tests that can integrate into Jenkins so that they run whenever new code is committed.</p>