I think that adding extra processing to JMeter to deal with processing client-side Javascript is counter-productive in general.
Although it would be convenient for some tests, it's a waste to keep reprocessing the Javascript in order to decide what URL to sample next - or to keep scanning the HTML to find out how to submit a particular form. Using the JMeter Proxy to record the session allows the work to be done by the browser when creating the test plan; it does not have to be repeated for every test. However, if anyone wants to develop an HtmlUnit sampler it could be done as an optional plugin. The HtmlUnit API seems fairly straight-forward - it could be called from a BeanShell sampler, at least as proof of concept. But I suspect that designing a GUI for it would not be trivial. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
