0.2.13 - 2020-12-21

Added

#1251 (Closes #1204) Add plugin for Amazon Kinesis (incubating)

"Incubating" means that the plugin is currently a work-in-progress and may change in the future releases.
New steps:

When I put record `$data` with partition key `$partitionKey` to Kinesis stream `$streamName`
When I start consuming records from Kinesis stream `$streamName`
When I drain consumed Kinesis records to $scopes variable `$variableName`

#1219 [vividus-plugin-datetime] Support timezone in toEpochSecond expression

Now the timezone is properly handled by toEpochSecond expression, e.g.:
#{toEpochSecond(2020-12-11T18:43:05+05:30)} -> 1607692385

#1244 [vividus-extension-selenium] Add case-insensitive sorting order options for step checking sorting

The full list of the supported options:

• ascending
• descending
• case-insensitive ascending
• case-insensitive descending

#1238 [vividus-plugin-mobile-app] Improve element visibility check for iOS native apps

The value of the attribute visible is taken into account: if true, element is considered visible

#1148 [vividus-plugin-browserstack] Add step to save network log to JSON context

Syntax:

When I save BrowserStack network logs to JSON context

#1216, #1249, #1263, #1265 [vividus-plugin-browserstack] Publish BrowserStack session link to Allure report

#1240 (Closes #1210) [vividus-plugin-aws-s3] Add step to set S3 object canned ACL

Syntax:

When I set ACL `$cannedAcl` for object with key `$objectKey` from S3 bucket `$bucketName`

Fixed

#1254 (Fixes #1252) [vividus] Fix variables resolution for the values with preceding }

#1237 (Fixes #1192) [vividus-plugin-web-app] Do not enable acceptInsecureCerts capability for Safari and IE

Safari and IE do not support acceptInsecureCerts=true capability, now it's considered when the capability is automatically applied if the proxy is used.

#1245 [vividus-plugin-web-app] Favor W3C browserVersion over JSON Wire version

The capability name is fixed for Edge, IE and Safari

#1264 (Fixes #1248) [vividus-plugin-web-app] Allow duplicate URL query and form data parameters

HTTP specification doesn't forbid usage of duplicate names in URL query and form data.