Version: 2.0
Changelog
#
2.0.0Released: Feb 2021
#
New features- Renovate the CLI to be more professional and user-friendly, for a better developer experience.
- Replace Puppeteer core with Microsoft's Playwright.
- Support running tests on different browsers including Chromium, Chrome, Firefox, and Webkit with browser setting or
--browser
CLI flag. - Support running tests with a custom version of Microsoft Edge, Google Chrome or any Chromium-based browsers by executablePath property in browserLaunchOptions setting or
--executablePath
CLI flag. - Support simulating multiple users on the local machine, with the ability to ramp up or down.
- Generate an HTML report of the final test results with
--export
CLI flag. - New APIs:
#
Enhancements- Add the ability to show screenshot on the terminal output (only for iTerms2 on MacOS) with
--show-screenshot
option when running test scripts locally. - Re-organize priorities order to get test setting values when running test scripts.
#
Deprecated--chrome
CLI flagchromeVersion
setting in Test Settingssuite
#
1.5.0Released: Jan 2021
#
New features- Ability to support multiple data files in a single test script
- Ability to debug Element script with VSCode
- Updated Puppeteer to the latest version (5.5.0)
- New APIs:
#
1.3.6Released: 24 Sep 2020
#
Enhancements- Show Element version and Node version in terminal while running tests
#
BugfixesElementHandle.uploadFile()
has been implemented but is not exposed in the APIBrowser.wait()
returns value of type boolean only
#
1.3.3Released: 18 Sep 2020
#
Bugfixes- Backward compatible with legacy test scripts (actionDelay & stepDelay time measurement unit)
--watch
option not workingconsoleFilter
settings not workingbrowser.sendKeys()
does not work ifTestSettings.waitUntil
is enabled- Error on authenticating with Flood from Element CLI
#
1.3.0Released: Aug 2020
#
New featuresExtended Step Types:
Hooks for setup and teardown
Support sending key combinations (
browser.sendKeyCombinations()
)Support authentication with Flood and lauching a flood directly from Element CLI
New command to generate a config file and run a test from a config file
Ability to set a Fail Status Code (ExitCode) if a test fails when running locally
#
Enhancements- Handle multiple tabs/windows (GitHub issue #47)
- Refactor code and fix dependencies life cycle issue (GitHub issue #176)
- Add
Until.elementTextDoesNotMatch()
- Support importing script helper from other node modules (GitHub issue #71)
- Make process.env reflect environment variables present when running
element run
(GitHub issue #104)
#
Bugfixes- Fix homebrew publish of Element (GitHub issue #135)
- Unable to use the command
element generate <file.ts>
(GitHub issue #165) - Setting
recoveryTries
does not work (GitHub issue #195) - Exit status of
element run test.ts
to reflect test passing/failing (GitHub issue #30) - Setting
screenshotOnFailure():true
does not create a screenshot on failure (GitHub issue #87) - Getting error
responded with status code 401. Element expected a status code 200-299 or 300-399
(GitHub issue #146)