Hi Peter, Thank you for good summary. I still have some questions.
On Tue, Mar 11, 2014 at 5:56 AM, Wang, Peter H <[email protected]>wrote: > *Q**:* > *I** have novice questions.* *could you explain relationship among below > modules?* > *chrome/test/chromedriver* > *third_party/webdriver* > *tools/telemetry/telemetry/core/backends/webdriver* > > A: > The "chrome/test/chromedriver" imports code from "third_party/webdriver". > Most of them are uglified JS code to help implement some instructions of > WebDriver. > They are the outside script to use WebDriver throught http request. Seems, > "telemetry" will invoke it to implement its function. > > Basic mechanism of "chromedriver" is like that: > Outside script à Chromedirver à Devtools interface of Browser > > So, any script can invoke "chromediver" by sending http request according > convention. > Could you answer about tools/telemetry/telemetry/core/backends/webdriver also? You explained only chrome/test/chromedriver and third_party/webdriver . *Q:* > *currently, perf test don't require chrome/test/chromedriver. what does > chrome/test/chromedriver add on > tools/telemetry/telemetry/core/backends/webdriver?* > *i.e. we can run perf test without chrome drive.* > *> ./tools/perf/run_measurement --browser=content-shell-release smoothness > tools/perf/page_sets/top_25.json --allow-live-sites* > *tools/telemetry/telemetry/core/backends/webdriver or > tools/perf/run_measurement is not enough? What's xwalk webdrive's goal?* > > A: > By my understanding, the main purpose of WebDriver is to provide a uniform > auto-test interface for Browsers. Especial to mimic some human > operations(e.g., click). > If you run above my command line, you can see that perf telemetry test mimics click and touch. it's why test name is "smoothness". I think we should know which features tools/perf support and which features it does not support, even if we need them. The first goal is just "catching up", means, to support WeDriver > instructions as other main Browsers (refer to > *http://docs.seleniumhq.org/download/*<http://docs.seleniumhq.org/download/>, > you can find Chromedriver, FirefoxDriver, BlackBerryDriver here). > Then, we'll try to involve some special instructions ("runtime" related?) > for xwalk, since, obviously, we are not a pure Browser. Maybe, we can try > to contribute to W3C or *Selenium* <http://docs.seleniumhq.org>, if our > suggestion has enough value and the implementation is solid. > > You concerned about how extract chromedriver from /chrome even if chromedriver depends on chrome extensions. I think you can extract chrome-independent chromedriver, which I believe most of them, and remains chrome-dependent part in /chrome. Best regards, DS
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
