For the first example with `givenConfigFromArgv()`, this is how you would use it in the test:

```js
it('was converted', function() {
  var config = givenConfigFromArgs(
    '--no-preload',
    '--save-live-edit',
    '--web-port=8081',
    '--web-host=127.0.0.2',
    '--debug-port=5859',
    '--hidden=["abc"]',
    '--stack-trace-limit=60'
  });

  expect(config.help, 'help value').to.equal(false);
  // etc.
});
```

Now that's easy to setup any argv scenario, it is probably better to split the test into multiple smaller ones. One of the benefits is that all expectations will be always verified. With the current approach, the first failed expectation aborts the test and remaining expectations are not run.

```js
it('handles --help', function() {
  var config = givenConfigFromArgs('--help');
  expect(config.help).to.equal(true);
});

it('handles --no-preload', function() {
  var config = givenConfigFromArgs('--no-preload');
  expect(config.preload).to.equal(false);
});

// etc.
```