title: Different browser behavior when pass .env variables in command for run tests
body: <p>It's not actually a problem, but I do not fully understand, what happened and why.</p>
  
  <p>I have this runner for my test. I test a React app.</p>
  
  <pre><code>let testcafe = null
  const isCiEnv = process.env.CI === 'true'
  
  const exit = async err =&gt; {
    console.log('Exiting...')
    if (testcafe) {
      console.log('Closing TestCafe...')
      testcafe.close()
    }
    console.log('Exiting process...')
    process.exit(err ? 1 : 0)
  }
  
  console.log('Is CI ENV: ', isCiEnv)
  console.log('Creating TestCafe...')
  
  createTestCafe('localhost', 1337, 1338)
    .then(tc =&gt; {
      testcafe = tc
    })
    .then(() =&gt; {
      console.log('Starting server...')
      return startServer()
    })
    .then(() =&gt; {
      console.log('Starting client...')
      return startClient()
    })
    .then(() =&gt; {
      console.log('Creating TestCafe Runner...')
      return testcafe.createRunner()
    })
    .then(runner =&gt; {
      console.log('About to start TestCafe Runner...')
      return runner
        .src([
          'test/e2e/fixtures/auth.js'
        ])
        .browsers({
          path: isCiEnv
            ? '/usr/bin/chromium-browser'
            : 'Chrome',
          cmd: isCiEnv
            ? '--no-sandbox --disable-gpu'
            : undefined
        })
        .screenshots('screenshots', true)
        .run({
          skipJsErrors: true,
          selectorTimeout: 25000,
          assertionTimeout: 25000
        })
    })
    .then(failedCount =&gt; {
      console.log('failed count:', failedCount)
      return exit(failedCount)
    })
    .catch(err =&gt; {
      console.error('ERR', err)
      return exit(err)
    })
  </code></pre>
  
  <p>In package.json i have this command for run test</p>
  
  <pre><code>"test:e2e": "HOST=0.0.0.0 NODE_ENV=test NODE_PATH=server babel-node test/e2e/index.js --presets stage-2"
  </code></pre>
  
  <p>But in the local environment, I run a test with this command</p>
  
  <pre><code>sudo REDIS_HOST=127.0.0.1 PORT=80 yarn test:e2e
  </code></pre>
  
  <p>That because on my local machine I have different config and I don't want to change it for everyone else.</p>
  
  <p>Usually, test runs in a different, clear version of the browser, without any account data, plugins and etc. But in this case, tests run in a new browser window, but with all plugins and my account name. But, it's doesn't have cookie and session auth data from the browser window, in which I usually work (because I authorized on-site in the working browser and doesn't auth in test browser). </p>
  
  <p>And if I change "Chrome" to "chrome" it stops run completely. Same behavior for Firefox and Safari.</p>
  
  <p>Earlier, without passing <em>REDIS_HOST</em> and <em>HOST</em>, it works as usual and runs in a clean new browser window. </p>
  
  <p>It's not a big problem, for now at least, but it's unexpected behavior and I don't understand, why it works this way. </p>
  
  <p>I'm not very familiar with Node and React, and maybe this related to them. </p>
  
  <p>Spec: macOS 10.12.5, Testcafe 0.20.3, Chrome 67</p>