Hi Sergio, a WebTest task is not designed to be accessed concurrently by multiple threads because it doesn't really make sense. Nevertheless multiple threads can be run in parallel, executing different <webtest> (or the same one). In fact this can already be done setting the wt.parallel.nbWorkers property, which will allows to specify the number of threads to use to execute the tests. This can probably be a starting point for you but it doesn't yet handle the ramp-up, schedule and delay between user "actions". I imagine that this can be simply implemented in a non intrusive way with a BuildListener. Last point: it would probably make sense to examine how to bind it to JMeter (implementing a Sampler for WebTest).
Don't hesitate to ask if you have additional questions. Cheers, Marc. -- Blog: http://mguillem.wordpress.com Sergio Bossa wrote: > Hi guys, > > I'm an happy WebTest user, and now I'd like to turn some tests I've > written into load tests. > Putting it simple, I just need to execute a whole webtest (but even a > group of steps would be ok) under concurrent load, by specifying the > number of simulated users (that is, concurrent executions), a ramp-up > period and optionally a schedule. > I've tried to write some custom steps, but there seems to be > synchronization problems, because WebTest APIs do not seem to be > designed for working in a concurrent environment. > > So, I'd like to have some suggestions by the WebTest developers about > how to implement such a feature. > Currently, the main problem seems to be that the WebtestTask Context > and the way it's used are not thread safe. > Obviously, if I'll implement that successfully, I'll contribute it > back to the WebTest community! > > Thanks, > Cheers, > > Sergio B. > _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
