Channels
#strikt
- c
christophsturm
08/22/2018, 6:05 PMthe first exception isstrikt.internal.opentest4j.AtomicAssertionFailure - c
christophsturm
08/22/2018, 6:05 PMand the second is a compound - r
robfletcher
08/22/2018, 6:05 PMwhat type of assertion is it? - c
christophsturm
08/22/2018, 6:06 PMcontainsExactlyInAnyOrder - c
christophsturm
08/22/2018, 6:08 PM - r
robfletcher
08/22/2018, 6:09 PMare the expected/actual outputs at least more meaningful? 😉 - c
christophsturm
08/22/2018, 6:10 PM-.js - c
christophsturm
08/22/2018, 6:10 PMthere are none now, which is better because both were null in 0.11.2 - r
robfletcher
08/22/2018, 6:10 PMright - r
robfletcher
08/22/2018, 6:11 PMso (I think) I have fixed #74 and broken #59 in the process - c
christophsturm
08/22/2018, 6:13 PMyeah but the exception type is different than before 0.11.2 before - c
christophsturm
08/22/2018, 6:13 PMso its a different bug that looks similar. it used to be 2 compoundfailures and now its one atomic and one compound - r
robfletcher
08/22/2018, 6:14 PMyeah, it's a compound that contains an atomic - r
robfletcher
08/22/2018, 6:14 PMI don't know why it then logs both as though they were separate - r
robfletcher
08/22/2018, 6:14 PMbut I guess both have an associated stack trace - c
christophsturm
08/22/2018, 6:16 PMmaybe write a test that captures the output and checks that it contains
only once, or once per failureExpect that - r
robfletcher
08/22/2018, 8:09 PMI really don't understand how that can have changed between now and 0.11.2 - c
christophsturm
08/22/2018, 8:10 PMit would be good to have a method that gives you back the opentest output for an exception - r
robfletcher
08/22/2018, 8:11 PMyes - c
christophsturm
08/22/2018, 8:11 PMi have never worked with opentest, is that somehting thats doable? - r
robfletcher
08/22/2018, 8:11 PMI don't see why not - c
christophsturm
08/22/2018, 8:12 PMwould you merge a pr that adds pitest support to the build? - r
robfletcher
08/22/2018, 8:13 PMsure - r
robfletcher
08/22/2018, 8:13 PMnever seen that before. Looks interesting - c
christophsturm
08/22/2018, 8:14 PMi love it, and it works great with kotlin now - r
robfletcher
08/22/2018, 8:14 PMI have considerable skepticism toward traditional coverage tools - r
robfletcher
08/22/2018, 8:14 PMbut this looks different - c
christophsturm
08/22/2018, 8:14 PMits pretty slow, but its also pretty fast for what it is doing - r
robfletcher
08/22/2018, 8:14 PMdoes it run out of band with the regular test suite? - c
christophsturm
08/22/2018, 8:14 PMbut the strikt test suite is fast anyway