New Release

[oleg-andreyev]

1.4.0 / 2019-08-28

Bug fixes:

• Don't use TABs, when triggering change JS event upon input value is change (fixes auto-complete control testing in Google Chrome)
• Fixed inability to manipulate windows when Selenium 3 with Firefox GeckoDriver was used
• The clickOnElement method wasn't working when Selenium 3 with Firefox GeckoDriver was used

Changes:

• Bumped requirement to PHP 5.4

New features:

• Allow uploading files to remote Selenium instances (e.g. SauceLabs, BrowserStack, etc.)
• Added getDesiredCapabilities method for fetching current desired capabilities

Testsuite:

• Don't test on PHP 5.3 (driver itself would likely continue to work on PHP 5.3 for some time)
• Adding testing on PHP 7.1, 7.2, 7.3 and 7.4beta
• Removed PhantomJS

Misc:

• Syn library is 0.0.3
• The setDesiredCapabilities method combines default capabilities with user provided ones
• Removed outdated default capabilities
• The setDesiredCapabilities method will throw an exception, when used on a started session

closes #284

[oleg-andreyev]

@aik099 @stof

[oleg-andreyev]

@aik099 after you will be okay with changes, I'll squash changes into one commit.

[aik099]

Merging, thanks @oleg-andreyev .

I don't have permission on Packagist (to update releases list) / GitHub (to create releases). This is where @stof should take on the lead. Also release date in CHANGELOG.md should be updated by @stof to represent actual date, when release will happen.

[timmillwood]

We were depending on "behat/mink-selenium2-driver": "1.3.x-dev", in our composer.json, now... 🔥

We'll update to ~1 or ~1.3 or dev-master, so just an FYI, as we might not be the only ones.

[greg-1-anderson]

@aik099 if you could tag the 1.4.0 release on GitHub, Packagist might take care of itself (if it's set to auto-update).

[aik099]

@greg-1-anderson , unfortunately I can't (see #311 (comment)).

I was hoping that @stof had corresponding permissions on Packagist/GitHub or that maybe @everzet can grant us both with such permissions for all Mink repositories (main one, test suite and all drivers).

[aik099]

Related discussion: #313 (doesn't mean we should change anything on our side).

[stof]

there is no change to do on Packagist. It picks the tag automatically.

[aik099]

there is no change to do on Packagist. It picks the tag automatically.

I could have guessed that since 1.3.x version was removed from Packagist automatically.

[oleg-andreyev]

@aik099 @stof so it's matter of pushing 1.4.0, so we need only to push this tag and create release on GitHub or it's also automated?

[aik099]

@oleg-andreyev , we need to create new release on GitHub side with correct notes and that will trigger tag creation and that will be picked up by Packagist.

[ryanaslett]

It would still be very good to actually push the tag in git, or make the tag on github as a release. Packagist will automatically update, but as of right now, there is no 1.4.0 release.

[greg-1-anderson]

c.f. #269