SeLite Settings (Components > Settings) allows easy custom configurations of Selenese scripts and Core extensions.


Selenium IDE can be extensively customised via Core extensions (written in Javascript). This way you add new Selenese commands and related functionality. Many extensions are worth reusing (by yourself, within your team or publicly). But then they often need to be configured, e.g. in regard of

Configuration interface

There was no convenient tool to

Most Core extensions can work with

Why not make your own

You could create custom GUI as an IDE extension of Selenium IDE through XUL overlays (in XML). But


It defines API and GUI that simplify management and sharing of configurations. They


You can

Associated sets and values manifests work only in standalone Selenium IDE, but not in SeleniumIDEtips > auxiliary Selenium IDEs inside browser (neither in Selenium IDE in browser sidebar).


Modules are schemas/templates of user’s configuration(s). They define each field:

Test developers define configuration modules (schemas) in Javascript. See SettingsFields and SettingsAPI.


User’s configuration(s) - values of the fields - are grouped in set(s). Those are stored in Firefox preferences. A module can have either

Settings also works without Selenium IDE and without manifests. So it may serve any Firefox extension.


Users can configure and override settings granularly via

For an example see SettingsInterface. If accessing configuration from Core extensions, see SettingsAPI.