Implement config file

[AndreyBelym]

No description provided.

[miherlosev]

After discussion, we decide to implement the following concepts:

• .testcaferc.json is a name of the configuration file.
• <browser_name> and <sources> parameters become optional. I.e. it's a possible to run TestCafe with testcafe command.
• configuration file are searched in the current directory (process.cwd()). If it exists then TestCafe reads the options from it.
• if user-defined options merge with options from the configuration file then TestCafe shows the inform message 'The values for from the configuration file will be ignored'.
• BREAKING CHANGES: at present, it's forbidden to use multiple calls for src, browsers and reporter methods (see code exampe). Instead of this, pass an array of the arguments to the appropriate method.
• Programmatic .reporter method supports the path to saved report as a second parameter

  return runner
      .reporter('json', '/reports/report.json')

• Configuration file uses a command line naming convention

.testcaferc.json

{
             'hostname': '123.456.789',
             'port1':    1234,
             'port2':    5678,
             'src':      'path1/folder',
             'ssl':      {
                 'key':                keyFile.name,
                 'rejectUnauthorized': 'true'
             },
             'browsers':    'ie',
             'concurrency': 0.5,
             'filter':      {
                 'fixture':     'testFixture',
                 'test':        'some test',
                 'fixtureGrep': '^Unstable'
             },
             'reporter': 'json'
         }

[miherlosev]

Implemented in #3147

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs or feature requests. For TestCafe API, usage and configuration inquiries, we recommend asking them on StackOverflow.