Releases: SeleniumHQ/selenium-ide
v3.4.2
v3.4.1
v3.4.0
Record/Playback session overhaul
- Playbacks now occur inside their own specific window, separating IDE activity from the usual browsing.
- Recording now dedicates a window to the test being recorded, windows being recorded will also show a badge on the bottom right corner.
- When switching projects, or closing the IDE, all windows created by the IDE will now close for you.
- While recording a new project, Selenium IDE will automatically add a
set window size
, this will set the window to the same size it was during recording.
Notable Changes
- New welcome dialog that guides you through the basic principles of the IDE.
- Automatic locators fallback, if the first locator fails after multiple retries, secondary locators found during recording will be used instead.
- New project button, created a new project for you on the fly (no need to restart the IDE).
- Added new commands
wait for element editable
,wait for element not editable
,wait for element present
,wait for element not present
,wait for element visible
,wait for element not visible
. ${KEY_ENTER}
is now submits forms (Chrome only).
v3.3.1
v3.3.0
Execute Script and Control Flow changes
When we've introduced execute script
and the different control flow commands, we've had the IDE browser playback in mind. But now, more than ever we are close to playback on WebDriver.
WebDriver's own driver.executeScript allows non-primitives variables to pass to it's scripts (objects, arrays, functions etc...), in order to support that we'll have to make a small change to the way scripts work.
Variable interpolation, no longer interpolates into strings.
That means, that when you execute a script, you no longer have to surround the variables with quotes, for example:
execute script | "${x}" + " world!"
will become execute script | ${x} + " world!"
.
Variables will automatically be treated according to their types, which will allows us to pass objects and arrays as well.
Breaking Change
Selenium IDE will try to mitigate the change by converting your scripts (e.g. "${x}"
-> ${x}
).
Upgrading selenium-side-runner
to latest version is required for newer scripts to work, this can be achieved by running:
npm i -g selenium-side-runner@latest
Fixes
- Changed play suite keyboard shortcut from
Control+Alt+R
toControl+Shift+R
- Fixed an issue with the
runner
not being able to send special keys withsend keys
command
v3.2.5
Notable Changes
- Move between test, suites and execution views with keyboard shortcuts (Command + 1, 2, 3)
- Play, stop, pause and all toolbar buttons now have keyboard shortcuts
Fixes
- Can open a file using Command + O (Control + O on Windows)
- Fixed an issue when dragging tests
- Fixed an exception that could cause when running parallel tests
- Fixed an issue with
assert
andselect
in the runner - Fixed an issue where the runner wouldn't glob files correctly on Windows
- Fixed an issue where pressing
x
while in debugger would run the rest of the test instead
v3.2.4
Notable Changes
- Step into button will enter debugger mode, allowing you to go step by step through control flow.
Fixes
- Pulled fixes from SideeX for recording, specifically around the recording of
type
. - Migrated DOMNodeInserted to MutationObserver (thanks @grese).
- Fixed an issue preventing control flow commands from working before opening a url.
- Added an error when trying to execute a project with no suites in the runner.
- Fixed a bug where
store
commands would hang playback if no variable name was given. - Fixed a bug where
end
commands wouldn't be colored green post execution.
v3.2.3
v3.2.2
v3.2.1
Critical bug fix for command playback that leverages implicit waits.