-
Notifications
You must be signed in to change notification settings - Fork 218
Add a package-level config file #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I take it this would be in YAML? |
Very likely. |
It should be possible
|
Agreed.
This is a separate feature request; it's out-of-scope for this issue. |
Could logging possibility be solved in a custom reporter when they are supported? |
Most of the output does come from the reporter. The test runner itself prints some errors for things like invalid command-line arguments, but anything that happens within a test is passed to the runner. |
This just loads a subset of the config that can be pased on the command line from the configuration file. The command line takes precedence over the config. See #46 [email protected] Review URL: https://codereview.chromium.org//1649663003 .
As more and more aspects of tests become configurable in various ways, it will become necessary to have project-level configuration files. These might be used for configuration that would otherwise be included declaratively on tests, since if all tests would share the same configuration it would be a drag to mark it over and over again. They might also be used for configuration that would otherwise be passed on the command-line, to make it easy to provide custom defaults on a per-package basis.
Some things the config file should definitely support:
As time goes on, more configuration will likely be added as well.
The text was updated successfully, but these errors were encountered: