Forum Discussion

ruvain's avatar
ruvain
12 years ago

Which tool to use and how?

Hello

I need some help to turn on my understandng

I had intsalled both Loadui and LoadUIWeb in order to perform some functional performance tests as well as later on some load tests. I suffer from some confusion as I don't know how to onduct the tests need and whch tool shold I be using.

First what am I sopoppssed to test? Its a web site offering touristical packages therefore, No add to cart, just browsing and some search performed on web site's datbase, Then each option (evry destinaton/ package) has it purchase button the egintes a check out procedure.

Now to the problems I encounter

1. LoadUIWeb allows a desired walktrough the web site and havng the actions recordedd for later playback on different loads - The problem I find is understanding the results and the presentaton.

2. Loadui much easier to operate BUT.... I don't find a way to record as I navigate using a browser like n the first tool. which s essential for simmulating the differen optons a custommer may wsh to choose (differen destnatons, dates and so that are crucal ffor this web ste as orders can be placed only on availabilty of the packages on specific dates).

3. In forst tool whch is meanto to render the HTML for tose who much "Visual orennted", renderng is full, (compared to what I've seen on tubes showng equivalent behavior of playback performed on tests recorded and executed in Vsual Studio 2012, in whch I understand renderning odf excuted tests is simillar to a 'hidden hand' operating the web browser automatically.

I'd lke please some guidance from community members as on how to plan and record the process decrbed avobe (browsing \ searching \ purchasing) on this webapplcaton/ webistewith one of this tools

Best Regards,

Ruvain

1 Reply

  • renatoathaydes's avatar
    renatoathaydes
    Contributor
    12 years ago
    LoadUI and LoadUIWeb tackle different, if related, technologies.

    LoadUI focuses on API load testing.

    LoadUIWeb focuses on browser-driven, HTTP-traffic load testing.

    If a website is designed such that it mostly makes calls to a certain API (most often REST APIs) and displays the results on the user's screen, then you have a good case to use LoadUI to test the API directly (because that's what you're interested in testing, not the ability of the browser to update records on the screen). In any other case, you should use LoadUIWeb.

    If you are able to simulate API calls using one of the LoadUI Runner Components (Web Page Runner, HTML Runner, Geb Runner etc.), it may be a good choice for testing your API-driven website.

    If the only way you can generate these API calls is by actually using a browser as a client and doing things manually, then clearly you should use LoadUIWeb.

    If you don't know anything about APIs or your website is not actually driven by APIs, you should use LoadUIWeb.


    Hope this helps.

    Renato