Skip to content

0.6.10 - 2024-05-20

Compare
Choose a tag to compare
@valfirst valfirst released this 22 May 14:57
· 451 commits to master since this release
release-0.6.10
685362b

Added

#5011 [vividus] Add expression #{extractSchemeFromUrl(..)}

New expression extracts the scheme component from the given URL.

#5013, #5016 (Closes #4664) Handle user info provided in URI by HTTP client

URI user info is handled in the fully-automated way while executing HTTP requests: user info provided as a part of URI is converted to basic authentication configuration for all HTTP methods.

#5029 [vividus-plugin-accessibility] Add ability to report each violation as separate assertion

New property:

accessibility.report-violations-as-assertions=false

#5048 [vividus-plugin-web-app-to-rest-api] Add ability to collect URLs not under base URL by FROM_SITEMAP transformer

New property:

transformer.from-sitemap.strict=true

defines whether invalid URLs will be rejected silently (where "invalid" means that the URL is not under the base URL, see sitemap file location explanation for more details).

Also strict transformer parameter is available, it's exclusively applicable to the transformer in which it is declared.

#5056 [vividus-plugin-mobitru] Add support of doInjection option at app installation

New property:

mobitru.do-injection=false

defines whether to inject special code into application to allow emulation of "touch id" action and QR code scan.

Changed

#5042, #5049 [vividus-plugin-lighthouse] Support latest Lighthouse

Fixed

#5012 [vividus-plugin-visual-tetsing] Keep order of ignore locators in visual configuration

#5050 [vividus-plugin-web-app-to-rest-api] Quietly handle non-encoded Sitemap URLs by FROM_SITEMAP transformer

According to standard all Sitemap URLs must be URL-escaped and encoded,
but there could be cases when production contains invalid URLs and it's needed to crawl websites, so FROM_SITEMAP transformer
must be able to handle such invalid URLs.