Bump spek-dsl-jvm from 2.0.8 to 2.0.16

[dependabot]

Bumps spek-dsl-jvm from 2.0.8 to 2.0.16.

Release notes

Sourced from spek-dsl-jvm's releases.

2.0.16

• Add support for IJ 2021.1
• Move artifact publishing to Maven Central.

2.0.15

Minor release to add support for IJ 2020.3

2.0.14

In 2.0.13 discovery and execution started using coroutines, which means they are not confined to a single thread anymore. This can be problematic as most test frameworks like mokk (and possibly mockito) rely on test execution to be confined in a single thread (#923). Another side effect is that the test execution order wasn't deterministic anymore as at any given point a coroutine can be suspended and control is given elsewhere. This release fixes both that issue, Spek is still using coroutines but the runtime ensures that a given test class will always be confined to a single thread.

2.0.13

This release adds several system properties to control how Spek does discovery and execution.

1. spek2.discovery.parallel.enabled - controls whether discovery is done in parallel or not, by default it is disabled. The presence of this property regardless of value will enable parallel discovery.

2. spek2.execution.parallel.enabled - controls whether execution is done in parallel or not, by default it is disabled. The presence of this property regardless of value will enable parallel execution.

3. spek2.execution.test.timeout - SPEK2_TIMEOUT is now deprecated (will be removed in 2.1.0) and will be replaced by this property. Controls how long a test can run before timing out, by default it is disabled - i.e tests won't timeout.

A note for parallel execution

Parallelism is at a class level not individual test scopes. Spek uses coroutines under the hood to execute tests in parallel, essentially spek2.execution.parallel.enabled just controls which CoroutineDispatcher is used. For parallel executions Dispatchers.Default is used, otherwise the one provided by runBlocking is used.

2.0.12

Patch release that adds support for IJ 2020.2 EAP and AS 4.0. The following AS and IJ versions are no longer supported:

• Android Studio 3.3
• Android Studio 3.4
• IntelliJ IDEA 2018.2
• IntelliJ IDEA 2018.3
• IntelliJ IDEA 2019.1
• IntelliJ IDEA 2019.2

2.0.11

Small patch release to disable timeouts by default. Having timeouts is a good idea but unfortunately the feature is not that customizable (i.e there's no way to disable timeouts via the IDE). Once its issues are fix I will consider in enabling it by default again.

2.0.10

This releases add supports for Android Studio 3.6 and IntelliJ IDEA 2020.1

New features

• Support for Android Studio 3.6
• Support for IntelliJ IDEA 2020.1 EAP
• New IDE inspection for spek classes without a no-arg constructor not marked abstract or any of the following annotations: @Ignore, @InstanceFactory. (#806)
• The IJ test runner now explicitly exits even if there are non-daemon threads around after test execution. (#848)

Deprecations and removals

• CachingMode.GROUP has now been deleted, this was deprecated a couple of release ago. (#798)

2.0.9

A minor release to support the release of IntelliJ IDEA 2019.3 (see #809).

New features

... (truncated)

Commits

• f660923 [2.0.x] Add support for IJ 2021.1 (#961)
• 4078fcd Publish to maven central (#951)
• 1f58a57 Add support for IJ 2020.3 (#941)
• 28c1329 Fix AS 4.6 ci build (#934)
• 88d54d2 Add AS 4.1 support (#932)
• 29d63f7 Ensure that discovery is done one class/spec per thread (#929)
• 1ca73ad Disable debug logging by default (#926)
• 15d9746 Ensure that only a single test class is executed per thread at any given time...
• 2da7cfa Drop AS 3.5
• d378a87 Fix failures
• 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)