toolisticon/jgiven-addons

kotlin extension for jgiven

toolisticon

Organizational stats

jgiven-addons's Issues

update jgiven 0.18.2

update gradle 5.6.3

We should let the version

upgrade to latest jgiven release

0.18.1 is out

release into maven central

Currently the library is released to jcenter. Using it in maven has two drawbacks comparing with maven central from sonatype:

• the jcenter repository nneds to be specified in the pom
• the jcenter is then used as a primary repo for all artifacts and it is remarkable slower than central

io.toolisticon.addons.jgiven:jgiven-scenario:0.5.1 is not usable out of Maven

Our internal project used

testImplementation("io.toolisticon.addons.jgiven:jgiven-scenario:0.5.1")

out of gradle, but the same dependency can't be resolved out of Maven.

upgrade to gradle 5.6.2

Add 2-Stage Action/Assert Scenario

Given/When steps are often mixed, but Then steps are completely different.

Introduce a ActionAssertScenario<ACTION, ASSERT>

add orchid docs and github pages

• setup orchid gradle in docs/ folder
• publish docs to gh-pages

reactivate gradle build script

see https://guides.gradle.org/creating-build-scans/

deactivated during #12

provide better docs

The readme should provide information how to use the library (include coordinates for both gradle and maven)

provide extension val for self()

its a nice pattern to use

fun `my step method`() = self().apply {
  // do stuff
}

but because self() is a platform type, the IDE complains that it could be null.

Avoid this by introducing

   val <X : Stage<X>> Stage<X>.self: X get() = self()!!

and use

fun `my step method`() = self.apply {
  // do stuff
}

Note: we could go one step further and privde st like stage {} which works like self.apply{}

release 0.6.0

remove dokka warnings for external classes

see Kotlin/dokka#284

build is full of

Can't find node by signature `com.tngtech.jgiven.junit5.SimpleScenarioTest`, referenced at 
io.toolisticon.addons.jgiven.junit5.DualScenarioTest (DualScenarioTest.kt:9). This is probably 
caused by invalid configuration of cross-module dependencies

mark obsolete when PR to jgiven is accepted and relased

jgiven-kotlin is a pendig PR for jgiven. Once this is established and supported by the core product, this addon lib will become obsolete.

release 0.5.2

gradle 6.1