Skip to content

CHANGELOG.md

Latest commit

 

History

History
280 lines (195 loc) · 6.84 KB

CHANGELOG.md

File metadata and controls

280 lines (195 loc) · 6.84 KB

@wdio/ocr-service

2.2.4

Patch Changes

  • 69d25fe: Multiple fixes:

    • update deps

2.2.3

Patch Changes

  • 2d033e8: update deps

2.2.2

Patch Changes

  • 4a4adf1: update deps

2.2.1

Patch Changes

  • a34dd5d: Update of deps

2.2.0

Minor Changes

  • 786248e: Upgrade Jimp to the latest major

2.1.1

Patch Changes

d76044f 🐛 Fix ERR_BUFFER_OUT_OF_BOUNDS for multiremote

Functions in utils such as getData.ts used the global browser, but this is not browser is not the browser making for example the ocrClick function call when the we are running in the multiremote context. This could lead to ERR_BUFFER_OUT_OF_BOUNDS error. This release fixes that error.

Committers: 1

2.1.0

Minor Changes

  • f5f8041: fix click duration for 0ms

Committers: 1

2.0.0

Major Changes

  • 9fdb2d2: feat: work with V9

1.0.5

Patch Changes

  • 85a1d82: # 🐛 Bug Fixes

    Fix issues:

    • 438: resizeDimensions not working
    • 448: hideElements and removeElements` don't work for native apps

    💅 Polish

    • update dependencies

    Committers: 1

1.0.4

Patch Changes

  • 0b01b64: ### @wdio/visual-service

    🚀 New Features

    Added Reporting output You now have the option to export the compare results into a JSON report file. By enabling the module option createJsonReportFiles: true, each image that is compared will create a report stored in the actual folder, next to each actual image result.

    The output will look like this:

    {
  "parent": "check methods",
  "test": "should fail comparing with a baseline",
  "tag": "examplePageFail",
  "instanceData": {
    "browser": {
      "name": "chrome-headless-shell",
      "version": "126.0.6478.183"
    },
    "platform": {
      "name": "mac",
      "version": "not-known"
    }
  },
  "commandName": "checkScreen",
  "boundingBoxes": {
    "diffBoundingBoxes": [
      {
        "left": 1088,
        "top": 717,
        "right": 1186,
        "bottom": 730
      }
      //....
    ],
    "ignoredBoxes": [
      {
        "left": 159,
        "top": 652,
        "right": 356,
        "bottom": 703
      }
      //...
    ]
  },
  "fileData": {
    "actualFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/.tmp/actual/desktop_chrome-headless-shellexamplePageFail-local-chrome-latest-1366x768.png",
    "baselineFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/localBaseline/desktop_chrome-headless-shellexamplePageFail-local-chrome-latest-1366x768.png",
    "diffFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/.tmp/diff/desktop_chrome-headless-shell/examplePageFail-local-chrome-latest-1366x768png",
    "fileName": "examplePageFail-local-chrome-latest-1366x768.png",
    "size": {
      "actual": {
        "height": 768,
        "width": 1366
      },
      "baseline": {
        "height": 768,
        "width": 1366
      },
      "diff": {
        "height": 768,
        "width": 1366
      }
    }
  },
  "misMatchPercentage": "12.90",
  "rawMisMatchPercentage": 12.900729014153246
}

    When all tests are executed, a new JSON file with the collection of the comparisons will be generated and can be found in the root of your actual folder. The data is grouped by:

    • describe for Jasmine/Mocha or Feature for CucumberJS
    • it for Jasmine/Mocha or Scenario for CucumberJS

    and then sorted by:

    • commandName, which are the compare method names used to compare the images
    • instanceData, browser first, then device, then platform

    it will look like this

    [
  {
    "description": "check methods",
    "data": [
      {
        "test": "should fail comparing with a baseline",
        "data": [
          {
            "tag": "examplePageFail",
            "instanceData": {},
            "commandName": "checkScreen",
            "framework": "mocha",
            "boundingBoxes": {
              "diffBoundingBoxes": [],
              "ignoredBoxes": []
            },
            "fileData": {},
            "misMatchPercentage": "14.34",
            "rawMisMatchPercentage": 14.335403703025868
          },
          {
            "tag": "exampleElementFail",
            "instanceData": {},
            "commandName": "checkElement",
            "framework": "mocha",
            "boundingBoxes": {
              "diffBoundingBoxes": [],
              "ignoredBoxes": []
            },
            "fileData": {},
            "misMatchPercentage": "1.34",
            "rawMisMatchPercentage": 1.335403703025868
          }
        ]
      }
    ]
  }
]

    The report data will give you the opportunity to build your own visual report without doing all the magic and data collection yourself.

    webdriver-image-comparison

    🚀 New Features

    • Add support to generate single JSON report files

    @wdio/ocr-service

    💅 Polish

    • Refactored the CLI to use @inquirer/prompts instead of inquirer

    Committers: 1

1.0.3

Patch Changes

💅 Polish

Update deps

Committers: 1

1.0.2

Patch Changes

  • 6e1e478: Fix contrast and languages

1.0.1

Patch Changes

  • 083ad82: Fixed OCR cli

1.0.0

Major Changes

  • a924dfc: # 🚀 New Feature

    Sometimes it can be hard to find an element in a mobile native app or desktop site, with an interactable Canvas, with the default WebdriverIO selectors. In that case, it would be nice if you would be able to use something like OCR (Optical Character Recognition) to interact with elements on your device/screen.

    The new @wdio/ocr-service service provides you with the option to interact with elements based on visible text. It will provide multiple commands to:

    • wait
    • search
    • and interact

    with an element, all based on text.

    The following commands will be added

    • ocrGetText

    • ocrGetElementPositionByText

    • ocrWaitForTextDisplayed

    • ocrClickOnText

    • ocrSetValue

      A CLI command will also be provided to pre-check text received from the image, this can be run by using the command npx ocr-service. For a demo check this video

      ocr-service-cli.mp4