>Do you have a rough idea, what the dsl would look like, or how the
>elements get mapped/detected to be a part of the dsl?
Commonly used elements have to be mapped manually for consistency reasons.
There might be a generic (string-like) approach to allow fine-tuning.
>Could you elaborate a bit more on your plan, or would the extra module
>be really an add-on?
I am not sure yet.
It might be that it would be good enough to keep the dsl classes side by
side with the corresponding elements.
In other words, creating a module for a couple of classes might not be that
justified.
>Do you have a rough idea, what the dsl would look like
Something behind the lines of
val plan = testPlan {
aggregateReport {
outputFile = File("...")
}
openModelThreadGroup {
schedule {
rate(50.0 / second)
random_arrivals(10.minutes)
}
transaction("hello") {
http("http://hello.example";)
http("http://world.example";)
}
}
}
println(plan.toJxm())
plan.execute()
Vladimir
