Hi Laurel,
On 27-Aug-09, at 2:07 PM, Laurel A. Williams wrote:
I've created a separate jMeter script for (2) to take sample data
and post it to the server side script, which then activates the
build script and eventually download the results. Again, I've had to
do this directly rather than simulate clicking the check boxes and
the submit button on the rendered page (since I don't get a rendered
page). As with (1) I'm not too worried about this, since I think the
biggest load concern is not the interaction with the page, but with
the submit and the response.
I'm pretty happy with the results so far, but feel like I should
check with others.
Does anyone see any reason why we should be concerned about the
parts of the process that I'm currently ignoring/bypassing?
No, I think you're taking a reasonable approach. As you say, the
biggest area for concern in terms of load is the work of creating a
custom build package on the server. Interaction with the Builder user
interface itself happens on the client, not the server, and can be
tested in isolation. We should be all set.
Thanks for explaining your approach to the list,
Colin
---
Colin Clark
Technical Lead, Fluid Project
http://fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
