Skip to content

Support for additional arguments for browser tests #127

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

Closed
zoechi opened this issue Mar 21, 2015 · 3 comments
Closed

Support for additional arguments for browser tests #127

zoechi opened this issue Mar 21, 2015 · 3 comments

Comments

@zoechi
Copy link

zoechi commented Mar 21, 2015

examples
content_shell --dump-render-tree some_test.html
chrome --allow-file-access-from-file some_test.html
Even better would be have dart-lang/test#23

@seaneagan
Copy link
Contributor

I'm hoping to add task-specific command-line args, see #116.

I assume you will prefer to use the unittest runner via a grinder test task or similar, in which case it depends how that accepts these options, I wonder if they can be in the config file.

@zoechi
Copy link
Author

zoechi commented Mar 30, 2015

Package level config file is probably to coarse-grained. I hope they will add additional configuration options for at list single test files. If the task-runner from the unittest package is used this issue might be redundant. I hope there will be a good integration.

@zoechi
Copy link
Author

zoechi commented Jun 3, 2015

I think this can be closed. This is something the test package should provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants