Is the kotest-bom working? There are already quite...

# kotest

[dave08]

Is the kotest-bom working? There are already quite a few modules in kotest and some have different versioning...

[sam]

Not sure if it is, but all versions should be 4.4.3 ?

[dave08]

Nope, the wiremock extension is at 1.0.1...

[sam]

Ah, ok so some of the extensions are moving to their own versioning / repo

[sam]

They won't be included in a BOM because they will be released on their own lifecycle

[dave08]

It might be a good idea to include them though, it just makes it much easier for users to just include them and upgrade them all in one place instead of looking to see if each one got an update. Anyways I suppose updating the bom in the kotest lifecycle with the most recent versions at that time is pretty reasonable, and anyone needing a more recent version can just look for it then...

[sam]

ok, I'll look at that. For now 4.4.3 == 1.0.1

[sam]

There's no new features in any of the externally released extensions

[dave08]

Yeah, I think kotest changes more often than they do...

[sam]

yeah, and it also means if there's a bug in something like wiremock extension, we're not waiting on a kotest release to get that bug fix out

[dave08]

Also, I think that module should use api instead of runtimeOnly in gradle to include wiremock, since part of its usefullness is configuring the stubs...

[sam]

raise a PR ?

[dave08]

Ok, I'll try to get to it tomorrow hopefully.

[dave08]

Btw I haven't forgotten about the testcontainer docs, I'm still working at finding the best way while I'm writing all those tests. I think having an option for start in first test used / stop in afterProject, might be a nice way to handle heavier images like dbs that take a while to initialize. I also currently have a wrapper for mysql and postgres I might try adding to the docs as an example.

[dave08]

Start can be run in beforeTest, testcontainers won't do anything if it's already started

[sam]

feel free to open tickets to suggest better syntax or other ideas as they come to you

[sam]

I tend to do a ticket vomit when I'm working on something and I'm not happy with the current state