This assumes that you’ve set up your web application and that there is an SeLite framework for it. You’ll need packages mentioned at Overview > Install. If you haven’t downloaded SeLite Components yet, getting them from source (which you’ll need anyway) may be faster.
Regardless of how you install Components, either
If your web application uses SQLite, you’ll get full SeLite functionality and smoother script data life cycle. You’ll be able to copy/restore
vanillaDB from within SeLite (via SettingsInterface). Otherwise you need to apply DataImport.
The following instructions are generic. For any application-specific steps see documentation of the respective framework.
You need to configure two main areas
There are two methods for this. The simpler one manages it through text file(s), as per SettingsManifests > Values manifests. Such configuration is easier to share and replicate than one administered through GUI. It also involves less steps and only one stage. You can still use GUI to review effect of values manifests (though it involves some extra steps).
An alternative method is Firefox profile-based configuration set(s), controlled through GUI. It can also override any values manifests. It’s done through SettingsManifests > Associations manifests. However, using GUI (for any part of configuration) usually requires the whole configuration to be in two stages.
This is already done for scripts that come with SeLite frameworks. If you’re using one of those frameworks, you can copy its values manifest
SeLiteSettingsValues.txt. Otherwise create it as a plain text file. Either way, you then need to adjust/enter value of field
See SettingsInterface > Managing mode. Select ‘Add a new value’ next to
bootstrapCoreExtensions. Point it to where you downloaded the framework JS file.
Add values for applicable following fields and for any custom fields/keys to
SeLiteSettingsValues.txt from the above
See descriptions below.
This has a dual purpose: to maintain profile-based configuration set(s), and to review effect of configuration set(s) or values manifest(s). If you want to use configuration set(s), create them if you haven’t done so (see above).
Before you use GUI, you need to load the bootstrapped framework. Start Selenium IDE and run any single command, e.g.
getEval | true. That has effect only for the current run of Firefox (so next time you start the browser you’ll need to repeat it in order to use GUI). Then you can configure roles and any framework-specific fields.
If you’d like to review configuration, open chrome:// URL chrome://selite-settings/content/tree.xul?selectFolder (or chrome://selite-settings/content/tree.xul?folder=/full/path/to/folder).
If you’d like to edit profile-based configuration set(s), open chrome://selite-settings/content/tree.xul. Then follow SettingsInterface and edit the following fields (if they apply to your framework):
scriptDB to get benefits of Overview > Data separation (in testing).
vanillaDB make sense only if the application data is in SQLite.
appDB select the SQLite file which is used by your application instance. (The file often has an extension other than
.db or even
scriptDB is for scripts.
vanillaDB will serve as a snapshot of
appDB, so that you can revert
testDB to it. Enter some new filenames (in a location where your account can create files).
vanillaDB, in Selenium IDE click at button . That reloads vanilla DB and script DB from app DB. (See SettingsInterface).
webRoot (it doesn’t matter whether it ends with a slash or not). Your scripts can access it via
SeLiteSettings.webRoot(). (This is a workaround for Selenium IDE issue ‘Base URL Should Allow Path’. Please, vote for it and also for other ThirdPartyIssues.)
Unless you are using GUI to maintain or review configuration, you can run scripts (cases or suites) right after you start Selenium IDE. You don’t need to run any single Selenese command first.
Locate, open and run a suite as per PackagedScripts.
If you have two or more frameworks, don’t switch between them during the same Firefox run. You need to restart Firefox (not just Selenium IDE). Reasons:
setTestDbKeeper(), but only one framework (or extension) can invoke it. See GeneralFramework > Preserving special values in script DB.