Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrade to kotest not reflected

See original GitHub issue

Running ./gradlew versionCatalogUpdate on main of https://github.com/oss-review-toolkit/ort shows

The following dependencies have later milestone versions:
 - io.kotest:kotest-assertions-core [5.3.1 -> 5.3.2]
     https://github.com/kotest/kotest
 - io.kotest:kotest-assertions-json [5.3.1 -> 5.3.2]
     https://github.com/kotest/kotest
 - io.kotest:kotest-extensions-junitxml [5.3.1 -> 5.3.2]
     https://github.com/kotest/kotest
 - io.kotest:kotest-framework-api [5.3.1 -> 5.3.2]
     https://github.com/kotest/kotest
 - io.kotest:kotest-framework-engine [5.3.1 -> 5.3.2]
     https://github.com/kotest/kotest

but still the upgrade of kotest is not reflected in the TOML changes. Any idea why? Is there a problem with test-only dependencies?

Issue Analytics

State:
Created a year ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

sschuberthcommented, Sep 14, 2022

I’m closing this as the original issue was solved.

0reactions

hvissercommented, Jun 28, 2022

Yeah that might be an option if the config isn’t locked at that point (and if that plays ball with configuration caching), though AFAIK the general recommendation is to avoid afterEvaluate, so I’m not 100% sure here. That would only be needed for the output formatter, the rest we’d still want to be allowed to be overridden in the build script.

Ideally I think it would be better to not do anything and throw an error, but that means that the setting needs to be checked at some point before the task runs.

Top Results From Across the Web

Changelog - Kotest

Any custom arbs that override this method should be updated. Any custom arbs that use the recommended arbitrary builders are not affected.

Test classes are not shown in correct package in test report

The problem is all test classes containing a "Some test scope" will have all the tests in that scope from all the classes...

I upgraded the Kotest version from lt kotest version gt 4 6 | Kotest

kotest.engine.spec.SpecInstantiationException: Could not create instance of class ComponentTestBadFlightReturned. Specs must have a public zero-arg constructor.

How to upgrade to Kotest 4.0? - Medium

Last but not least. Finally, I needed to update the Kotlin language version. There was a problem in the runtime. The definition of...

Kotest test factory and beforeSpec - kotlin - Stack Overflow

Problem is that beforeSpec is not invoked inside test factory, hence I'm currently using a dirty workaround by doing init stuff in the...