✨ feat: implement scalatest integration #373
Conversation
gaeljw
added
⚡ enhancement
| options: T | ||
| ): Try[RuntimeOptionsBuilder] = { | ||
| Try { | ||
| // TODO verify how getClass behaves with the trait |
There was a problem hiding this comment.
So let`s say
trait CucumberSuiteOptions
trait CucumberSuiteOptionSpf extends CucumberSuiteOptions
def parse[T <: CucumberSuiteOptions](options: T with CucumberSuiteOptions): String = {
val clazz = options.getClass
clazz.toString
}
parse(new CucumberSuiteOptionSpf{}) // val res3: String = class rs$line$16$$anon$1
In Welcome to Scala 3.3.1 (17.0.2, Java OpenJDK 64-Bit Server VM).
|
|
||
| class RunCukesTest extends CucumberSuite with CucumberSuiteOptions { | ||
|
|
||
| override def featuresPath: Seq[String] = Nil |
There was a problem hiding this comment.
what about Functor Option to express something that could be ... could be
| parse(options) match { | ||
| case Success(value) => value | ||
| case Failure(exception) => | ||
| println( |
There was a problem hiding this comment.
are we sure that we would like to have this print in SOUT asis ?
There was a problem hiding this comment.
Probably not but so far I just got inspired from the cucumber-junit module and copy/pasted stuff from there.
| private val context: CucumberExecutionContext | ||
| ) extends Suite { | ||
|
|
||
| private val children: Seq[PickleSuite] = { |
There was a problem hiding this comment.
How many levels of hierarchy can Scala test express? If more than 2, it might be worthwhile to match the layout in the feature file. Representing only the feature and pickles was a JUnit 4 limitation.
|
@dfurmans @mpkorstanje this is a very first draft, I don't even remember if it compiles yet 😅 No need for a deep review for now I guess. I don't have plans to work on it in the coming weeks, if anyone wants to take over and complete it, I'm perfectly fine with that :) |
|
Alright, no worries! I'm currently working on some stuff in cucumber for junit 5 that is somewhat related. |
No description provided.