Do not search for implementation functions of Selenese action commands case-sensitively. Actions (i.e. ones with primary forms that don’t start with
get neither with
is and that are not like
do. E.g. command
xyz is implemented in function
strict mode. Otherwise the function will be in the Selenium global scope (i.e. outside of Core scope) - then you need to see ExtensionSequencer > Core extensions loaded twice.
do. (E.g. action
abcDef is implemented by function
doAbcDef.) Don’t have primary Selenese action names themselves in form
getXyz, isXyz or
isXyzPresent (i.e. implemented by functions
doGetXyz, doIsXyz or
doIsXyzPresent, respectively), unless you have a very good reason. Such names would imply that the command is a getter or checker rather than an action. They would suggest that there are other auto-generated Selenese commands for them (
assertXyz etc., as per ClassicSelenese > Auto-generated Selenese commands), but those wouldn’t exist.
Don’t define the second parameter (usually called
value) for Selenese getter commands. See Documentation and handling of Selenium.prototype.getXYZ functions - Se IDE.