Limitation for GatlingHttpFunSpec

Hi Gatling Devs,

Am playing with your prototype Spec2 and general test demo at

Delving into the GatlingFunSpecExample, I ascend two levels into GatlingFunSpec to see that the only entry point is the
public method spec(). There is no access to the scenario so that one could define one’s usage patterns via inject()… as it
does not seem possible to override the default testScenario:

private[this] lazy val testScenario = scenario(this.getClass.getSimpleName)

private def setupRegisteredSpecs() = {
  require(specs.nonEmpty, "At least one spec needs to be defined")

Have I missed something?


The FunSpec is a first draft.
Improvement ideas and contributions welcome!