You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
classSeqImplicitsDoctestextendsScalaCheckSuite {
defsbtDoctestTypeEquals[A](a1: =>A)(a2: =>A): _root_.scala.Unit= {
val_= () => (a1, a2)
}
defsbtDoctestReplString(any: _root_.scala.Any): _root_.scala.Predef.String= {
vals= _root_.scala.runtime.ScalaRunTime.replStringOf(any, 1000).init
if (s.headOption ==Some('\n')) s.tail else s
}
test("SeqImplicits.scala:275: sampleN") {
importjava.util.UUIDimportcom.mypackage.implicits.SeqImplicits.RichIterable
property("property at line 282: (s: Seq[UUID], n: Int) => (0 <= n && n <= s.size) ==> (s.sam ...") {
forAll((s: Seq[UUID], n: Int) => (0<= n && n <= s.size) ==> (s.sampleN(n).size == n))
}
}
}
The property-based test do not get executed. If I understood Munit's property method correctly, it registers a property-based test. But here it happens inside of another test which is now getting executed, it is now too late.
I looked into trait TestGen but the current architecture doesn't appear to be compatible with the way Munit expects property-based tests. That is, the abstract generatePropertyExample method is used at the same level as generateExample which only gets placed inside generateTestCase as the test body.
The text was updated successfully, but these errors were encountered:
I have an doctest like the one below:
But since the test code is generated as below:
The property-based test do not get executed. If I understood Munit's
property
method correctly, it registers a property-based test. But here it happens inside of another test which is now getting executed, it is now too late.I looked into
trait TestGen
but the current architecture doesn't appear to be compatible with the way Munit expects property-based tests. That is, the abstractgeneratePropertyExample
method is used at the same level asgenerateExample
which only gets placed insidegenerateTestCase
as the test body.The text was updated successfully, but these errors were encountered: