Changelog

1.5.0

Released: Jan 2021

New features

• Ability to support multiple data files in a single test script
• Ability to debug Element script with VSCode
• New APIs:
  • browser.scrollBy()
  • browser.scrollTo()
  • browser.getUrl()

1.3.6

Released: 24 Sep 2020

Enhancements

• Show Element version and Node version in terminal while running tests

Bugfixes

• ElementHandle.uploadFile() has been implemented but is not exposed in the API
• Browser.wait() returns value of type boolean only

1.3.3

Released: 18 Sep 2020

Bugfixes

• Backward compatible with legacy test scripts (actionDelay & stepDelay time measurement unit)
• --watch option not working
• consoleFilter settings not working
• browser.sendKeys() does not work if TestSettings.waitUntil is enabled
• Error on authenticating with Flood from Element CLI

1.3.0

Released: Aug 2020

New features

• Extended Step Types:

  • step.if()
  • step.unless()
  • step.while()
  • step.repeat()
  • step.once()
  • step.skip()
  • step.recovery()

• Hooks for setup and teardown

  • beforeAll()
  • beforeEach()
  • afterEach()
  • afterAll()

• 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)