Browsers can now be run in headless mode via the arguments in the browser provider configuration. Tests recorded or built with the new SeleniumIDE (3.x) can now be imported into MuseIDE from the .side file.
Additions and improvements
- Import new SeleniumIDE format files (.side)
- BrowserProvider now has an arguments field that is passed to the browser startup command. E.g. “–headless”
- ValueSourceDescriptors can now have a default value. This is useful, for example, on optional step parameters that should have a ‘true’ value when used.
- All events are shown in the event log table, including those before the first step starts.
- Updated to Selenium 3.11
- Improve command-line output from tests
- New WebdriverCapture plugin can collect screenshots, page content and log files for each step.
- New EventLogWriter plugin writes events to disk as-they-are-received, instead of at the end of the test. Very useful when a browser hangs or test crashes due to unhandled errors.
- Fixed bug with copy and multiple-paste that caused step-ids to be duplicated, leading to UI corruption when stepping through a test.
- Fix: Test Suite plugin failures do not show message to user (command-line or log file).
The 0.13 release (coming soon) adds the ability to import tests in .side files – the format created by the newest SeleniumIDE (3.x). This is an enhancement to the existing import, which could import the previous SeleniumIDE format (.html).
To import SeleniumIDE tests into your project:
- Press the Import button in the project navigator
- Select the .side file
- Select the tests to import
- Press the Import N tests button
When selecting tests to import, the test name (assigned in SeleniumIDE) will be converted into a filename-friendly resource id. The new id is shown on the import screen and id conflicts will be indicated:
When selecting the tests to import, also you can see if tests have any unrecognized commands:
Tests with unsupported commands can still be imported – they will be noted in the step editor in MuseIDE along with their command names and parameters. You can then decide if these steps are necessary (SeleniumIDE records a lot of unnecessary steps). If you find there are critical commands that are unrecognized, please contact us. Frequently, these commands are easy to add and we can issue an update within a day or two.
The test editor indicates steps that use unrecognized commands with a red warning icon:
In this case, the mouse and scroll steps are unnecessary. Removing those steps results in a test that executes successfully. Your mileage may vary.
The ability to import .side files means you can record a workflow in SeleniumIDE and then quickly import into a MuseIDE test, rather than building the tests step-by-step. SeleniumIDE is available as an extension for Firefox and Chrome.