Skip to content

Releases: spekframework/spek

2.0.19

22 Aug 01:57
04a479e
Compare
Choose a tag to compare

2.0.18

29 Mar 20:44
9f0749b
Compare
Choose a tag to compare

What's Changed

  • Update Kotlin, gradle-intellij-plugin and add support for IJ 2021.3 by @raniejade in #991

Full Changelog: 2.0.17...2.0.18

2.0.17

28 Aug 12:15
9f17abf
Compare
Choose a tag to compare
2.0.17

2.0.16

13 Apr 06:40
f660923
Compare
Choose a tag to compare
  • Add support for IJ 2021.1
  • Move artifact publishing to Maven Central.

2.0.15

14 Dec 05:53
1f58a57
Compare
Choose a tag to compare

Minor release to add support for IJ 2020.3

2.0.14

14 Nov 23:34
28c1329
Compare
Choose a tag to compare

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

12 Sep 03:14
Compare
Choose a tag to compare

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

05 Jul 03:51
492fcbd
Compare
Choose a tag to compare

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

04 Jun 09:16
dc7f2ae
Compare
Choose a tag to compare

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

07 Mar 03:26
9edff95
Compare
Choose a tag to compare

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)