Unable to run Webdriver tests from test.dart

[efortuna]

The original test.py script allowed you to run Selenium WebDriver tests from test.py by specifying --component=webdriver. This does not yet seem to be implemented for test.dart.

Examples, the following command worked with test.py: (apologies for the length of this command; I gave full paths to illustrate what I was doing)

./tools/test.py --component=webdriver --flag=ff --flag=--frog=/Users/efortuna/perfChart/dart/xcodebuild/Release_ia32/dart-sdk/bin/frogc --report --flag=--froglib=/Users/efortuna/perfChart/dart/xcodebuild/Release_ia32/dart-sdk/lib --timeout=20 --progress=color --mode=release language

The following command, however:
xcodebuild/Release_ia32/dart tools/test.dart --component=webdriver --flag=ff --flag=--frog=/Users/efortuna/perfChart/dart/xcodebuild/Release_ia32/dart-sdk/bin/frogc --report --flag=--froglib=/Users/efortuna/perfChart/dart/xcodebuild/Release_ia32/dart-sdk/lib --timeout=20 --progress=color --mode=release language

Causes this to print out:
Unknown value (webdriver) for option --component

[madsager]

Thanks Emily! Bill is looking into that. We will add support for this before removing the old test.py scripts.

---

Set owner to @whesse.
Added Accepted label.

[efortuna]

Also, you may have this functionality already in test.dart, but just as a heads up for understanding the command I was running, you'll notice I'm (ab)using "--flag" (which in the python script goes to vm_flags) to specify additional information. I'm not the only one that has used this -- Siggi is using it for his "frogium" components as well, I believe.

[DartBot]

This comment was originally written by whe...@gmail.com

---

Yup, this is the one feature still missing. It should be easy to add tomorrow, now that I've refactored EnqueueBrowserTest. Thanks for the heads-up on --flag - I would probably have missed that.

[whesse]

Adding the --froglib-path and --frog-path variables remains to be done.

[whesse]

Added Fixed label.