• robfletcher

    robfletcher

    1 year ago
    please tell me I don’t have to deal with Nexus repos and their awful UI again
    robfletcher
    a
    4 replies
    Copy to Clipboard
  • robfletcher

    robfletcher

    1 year ago
    Also 0.29.0 is now out which drops
    strikt-java-time
    in favor of a more general
    strikt-jvm
    . Some of the JVM-specific stuff from
    strikt-core
    also moves to the new module.
    robfletcher
    christophsturm
    17 replies
    Copy to Clipboard
  • a

    alorma

    1 year ago
    Hey. looking at the errors, i thouht.... instead of show this:
    com.infojobs.app.base.datasource.cachedb.DateConverterTest > should convert Instant objects FAILED
        org.opentest4j.AssertionFailedError: ▼ Expect that 2021-02-24T14:04:22.023Z:
          ✗ is equal to 2021-02-24T14:04:22.023564Z
                  found 2021-02-24T14:04:22.023Z
    Wouldn't be better to show like this:
    com.infojobs.app.base.datasource.cachedb.DateConverterTest > should convert Instant objects FAILED
        org.opentest4j.AssertionFailedError:
        ▼ Expect that 2021-02-24T14:04:22.023Z:
          ✗ is equal to 2021-02-24T14:04:22.023564Z
                  found 2021-02-24T14:04:22.023Z
    ????
    a
    robfletcher
    +1
    17 replies
    Copy to Clipboard
  • r

    rocketraman

    1 year ago
    I have a function under test that takes an
    Iterable<T>
    and returns a subset of that given a single element
    T
    . For example, assume my function has signature
    fun <T> Iterable<T>.priorAdjacent(elem: T): List<T>
    . Currently use the pattern:
    expectThat(elems) { get { priorAdjacent(elems[3]) } isEqualTo elems.slice(1..2) }
    which reads nicely and produces understandable failure messages. That being said, is that the best approach?
    r
    robfletcher
    +1
    13 replies
    Copy to Clipboard
  • christophsturm

    christophsturm

    1 year ago
    maybe its time for a new strikt release, the main branch has no transitive dependencies on jcenter.
    christophsturm
    robfletcher
    3 replies
    Copy to Clipboard
  • christophsturm

    christophsturm

    1 year ago
    there are tests that sometimes very rarely fail and it stays a mystery why they do. i wonder if it makes sense to have support for outputting more diagnostic output in that case
    christophsturm
    4 replies
    Copy to Clipboard
  • s

    SimonT

    1 year ago
    Hello, is there any way to use coEvery with Strikt? My intento is to verify if a method is called x times and then do an expectThat for another assertions, and I want to get se see everything that fails
    s
    robfletcher
    2 replies
    Copy to Clipboard
  • christophsturm

    christophsturm

    1 year ago
    I wonder if it would be cool to add special handling to isEquals failures that have the same string output.
    christophsturm
    robfletcher
    7 replies
    Copy to Clipboard
  • christophsturm

    christophsturm

    1 year ago
    are there matchers for bigdecimal?
    christophsturm
    robfletcher
    7 replies
    Copy to Clipboard
  • christophsturm

    christophsturm

    1 year ago
    what do you think about something like
    val parsed=expectThat("""{"abc":"def"}""").isValidJsonFor<MyType>()
    christophsturm
    robfletcher
    5 replies
    Copy to Clipboard