Add configurable platform support

[stevenroose]

Chromium and Chrome should have similar run properties. However Chromium is open-source, while Chrome is branded. This makes Chromium more widely available on Linux systems and the preferred choice of many Linux users.

Since they would probably only differ in the name of the command, it's easy to add Chromium support as a separate platform, but alternatively, the chrome platform could just use google-chrome or chromium, whichever is available. (I assume something similar should already happen in order to support google-chrome-beta.)

[nex3]

I'm going to retarget this issue to refer to general support for configuring platforms. This is blocked on #46, since that's where the configuration will live.

I envision the ability to define new platforms that are small configurations of existing ones, like so:

platforms:
  chromium:
    type: chrome
    name: Chromium
    executable: chromium

The "type" is an existing platform whose spawning logic can be re-used. The name is an optional human-readable name for that platform, and the executable is the executable name.

In practice, finding the executable will likely be a little more complicated than that, because different operating systems have different locations and executable path conventions. We'd probably want to support something like this:

platforms:
  chromium:
    type: chrome
    name: Chromium
    executable:
      linux: chromium
      mac_os: /Applications/Chromium.app/Contents/MacOS/Chromium
      windows: Chromium\Application\chrome.exe

Absolute paths would be resolved absolutely, executable names would use the executable path, and for Windows in particular relative paths would check against LOCALAPPDATA, PROGRAMFILES, and PROGRAMFILES(X64).

You'd also be able to use this to override the executable locations of existing platforms:

platforms:
  dartium:
    executable:
      linux: dartium
      mac_os: /Applications/Dartium.app/Contents/MacOS/Chromium
      windows: Dartium\Application\chrome.exe

Although it would probably be better style to put that in the global config file (#63).

[stevenroose]

That sounds awesome!

[nex3]

Another thing I should mention: derived platforms would inherit the platform selectors of their parents, so @TestOn("chrome") would also allow a test to run on Chromium. They would also introduce their own platform selector variable, so @TestOn("chromium") would work as well, and would not allow plain Chrome.

[nex3]

Initial configuration file support has landed, so this is no longer blocked.

[StepFischer]

Is the topic of configurable platforms still in the work or is it abandoned?

[nex3]

This is definitely still something we plan to do (which is why this issue is still open 😉).