Marionette uses a small list of Selenium atoms to interact with web elements. Initially those have been added to ensure a better reliablity due to a wider usage inside the Selenium project. But by adding full support for the WebDriver specification they will be removed step by step.
Currently the following atoms are in use:
Update required Selenium atoms¶
In regular intervals the atoms, which are still in use, have to be updated. Therefore they have to be exported from the Selenium repository first, and then updated in atom.js.
Export Selenium Atoms¶
The canonical GitHub repository for Selenium is
so make sure to have a local copy of it. For the cloning process
it is recommended to specify the
--depth=1 argument, so only the
last changeset is getting downloaded (which itself will already be
more than 100 MB). Once the clone is ready the export of the atoms
can be triggered by running the following commands:
% cd selenium % ./go % python buck-out/crazy-fun/%changeset%/buck.pex build --show-output %atom%
%changeset% corresponds to the currently used version of
%atom% to the atom to export. The following targets
for exporting are available:
For each of the exported atoms a file can now be found in the folder
code including dependencies for the atom wrapped into a single function.
To update the atoms for Marionette the
atoms.js file has to be edited. For
each atom to be updated the steps as layed out below have to be performed:
- Remove the contained license header, which can be found somewhere in the middle of the file.
- Update the parameters of the wrapper function (at the very top)
so that those are equal with the used parameters in
- Copy the whole content of the file, and replace the existing
code for the atom in
Test the changes¶
To ensure that the update of the atoms doesn’t cause a regression a try build should be run including Marionette unit tests, Firefox ui tests, and all the web-platform-tests.