`ng test` should accept argument for karma configuration file

[traviskaufman]

As discussed with @hansl, currently there is no way to specify the location of karma.conf.js when running ng test. We should allow this to be specified so that angular-cli can be used with projects that do not place config files in their default locations.

[hansl]

Actually the solution would not be argument but a metadata with sensible default. I'll work on this.

[Brocco]

Does this make a lot of sense given that the file is generated by the CLI and will therefore be in a consistent location?

[hansl]

Projects might want to move it (e.g. Material2 has it in test/). There should be a way to set its location in the package.json.

[Brocco]

Point taken.
Then I agree we should store the location within package.json
Is there a scenario where we would need to support multiple configuration files? I'd prefer to cover all those scenarios up front rather than have multiple ways to store the config info.

[hansl]

Yeah I'm not 100% sure about multiple test files, but we can revisit.

[riscie]

The option --config-file seems to already be there?

--config-file (String) aliases: -c <value>, -cf <value>

Although, riscie, those aliases/options do not appear to work.

[krotscheck]

An example scenario for multiple test configs:

• karma.conf.js - Regular unit tests, run in Phantom or whatever browsers are passed in.
• karma.browserstack.conf.js - CI-run automated tests against all browsers in our preflight and postflight jobs.

[Brocco]

This is something I can take a look at over the next few days.