Skip to content

Releases: imsardine/winappdriver

v0.2.1

24 Aug 02:40
Compare
Choose a tag to compare

Bug Fixes

  • #12, #17, #21 Failed to activate store apps due to ActivateStoreApp.exe could not be found.

v0.2

15 Aug 02:17
Compare
Choose a tag to compare

New Features

  • Get current window handle.
  • Get all window handles.
  • Change focus to another window.
  • Get the current page/window title.
  • Close the current window.
  • Add support for ID locator strategy.
  • Get location and size of a certain element.
  • Check if an element is visible on the screen.
  • Get tag name of a certain element.
  • Get location and size of a certain window.
  • Check if an element is enabled.
  • Check if an element is selected.
  • Get attribute values of an element.
  • Add support for tag name locator strategy.
  • Add support for drag & drop
  • Add support for double click.
  • Add support for clearing text.
  • Add support for scrolling into view.
  • Highlight elements that match search criteria. (overlay)
  • Visualize the target before clicking an element.
  • Implement implicit wait.
  • Implement getting active element and comparing two elements.
  • Introduce a configurable delay between keystrokes.

Bug Fixes

  • Modern apps are not in the list of top-level windows
  • Indefinite loop while dumping Twitter sign-in page.
  • Backup states (if necessary) even if the app cap is not provided.

Enhancements

  • Move the mouse pointer more smoothly.
  • Set value by sending keystrokes.

The first public release

05 May 10:21
Compare
Choose a tag to compare
Pre-release

Features:

  • A package installer that gets you started quickly.
  • Support of modern UI apps (a.k.a store apps, universal apps, or Windows apps).
  • Support of desktop applications, including the handling of UAC elevation prompts.
  • Native keystrokes and mouse clicks.
  • Reset strategies that help to put your testing environment into a known state before running tests against it.
  • Locator strategies that are relevant to non-web applications, including ID, name, class name, and even XPath.
  • With the help of retrieving page source in XML, Inspect that comes with Windows SDK is not needed to figure out the right locators for target UI elements.