Bump lucatume/wp-browser from 2.2.31 to 2.6.0

[dependabot-preview]

Bumps lucatume/wp-browser from 2.2.31 to 2.6.0.

Release notes

Sourced from lucatume/wp-browser's releases.

2.6.0

Added

• support, in WPTestCase, for the @runInSeparateProcess annotation to run test methods in separate PHP processes; fixes #410

2.5.7

Fixed

• Codeception required version erroneously set in prev version of composer.json file

2.5.6

Added

• check in the codecept init wpbrowser command to check and report missing Codeception 4.0 to the user during initialization, fixes #412

2.5.5

Changed

• refactoring to pass phpstan level 1 and 2 checks.

2.5.4

Fixed

• an issue with .env files handling that, when the vlucas/phpdotenv package is not required, would incorrectly set up the test environment.

Changed

• some refactoring to pass phpstan level 0 checks.

2.5.3

Added

• the WPDb.letCron configuration parameter to control whether wp-cron processes should be allowe to spawn during tests or not (new default).

Fixed

• the WPDb module will set up the database to prevent wp-cron requests from being spawned during tests, fixes #363.
• env file parsing issues reported, fixes #398.

Changed

• following changes to how the WPDb module sets up the database at the start of tests (and between tests), wp-cron process will not be spawned during tests unless the WPDb.letCron configuration parameter is set to true.

2.5.2

Fixed

• added Dotenv\Dotenv polyfill class to avoid back-compatibility issues w/ projects not requiring vlucas/phpdotenv explicitly and using env files for tests configuration.

2.5.1

Fixed

... (truncated)

Changelog

Sourced from lucatume/wp-browser's changelog.

[2.6.0] 2020-06-08;

Added

• support, in WPTestCase, for the @runInSeparateProcess annotation to run test methods in separate PHP processes; fixes #410

[2.5.7] 2020-06-02;

Fixed

• Codeception required version erroneously set in prev version of composer.json file

[2.5.6] 2020-06-02;

Added

• check in the codecept init wpbrowser command to check and report missing Codeception 4.0 to the user during initialization, fixes #412

[2.5.5] 2020-05-25;

Changed

• refactoring to pass phpstan level 1 and 2 checks.

[2.5.4] 2020-05-22;

Fixed

• an issue with .env files handling that, when the vlucas/phpdotenv package is not required, would incorrectly set up the test environment.

Changed

• some refactoring to pass phpstan level 0 checks.

[2.5.3] 2020-05-15;

Added

• the WPDb.letCron configuration parameter to control whether wp-cron processes should be allowe to spawn during tests or not (new default).

Fixed

• the WPDb module will set up the database to prevent wp-cron requests from being spawned during tests, fixes #363.
• env file parsing issues reported, fixes #398.

Changed

• following changes to how the WPDb module sets up the database at the start of tests (and between tests), wp-cron process will not be spawned during tests unless the WPDb.letCron configuration parameter is set to true.

[2.5.2] 2020-05-13;

... (truncated)

Commits

• 39cf1ee doc(CHANGELOG.md) update to version 2.6.0
• 8c8e0c8 doc(docs) add entry about separate PHP processes
• 2b36530 fix(src) trait duplication issues
• e1bb2f1 test(dbunit) update snapshots
• c460ad9 refactor(src) conflate trait code
• 44ff603 fix(src) handling of plugins themes while in separate proc
• 8d5fd0f refactor(src) proxy Compatibility::phpunitVersion method to func
• ed9d15d build(phpstan) ignore compat functions
• 020491e build(Makefile) update name of excluded file
• 021648f Merge branch 'master' into feat/wptestcase-isolation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #31.