Scenarios for load

Artificial

                       

Overview

• Single-user

This article describes the various scenarios for load testing an application.

“S01” and such in file refer to these values which designates the file’s usage.

Single-user

• S01-Not available – “System not available” pages are served by an infrastructure server, not the app under test because that is served when the app doesn’t work. Without this page being available, users may get diverted to their ISP’s marketing page.

  PROTIP: Such a page should have a way to contact you, such as an email and phone number.

  PROTIP: This site shows some creative pages.

• S02-404 Not Found – A “Page Not Found” is shown when a visitor adds something strange after the host name. On Apache web servers, this page is specified in the .htaccess file.

  PROTIP: Amazon puts up a picture of cute pets to elicit sympathy.

  PROTIP: On this page, provide a text search form, a menu, a link to your site’s landing/home page.

  PROTIP: Put a simple form on the page to allow visitors a way to provide feedback about the broken link.

  PROTIP: Review your web log to identify frequently mistyped URLs so that you can even put links to the correct location directly on the page. That is a better UX so that visitors quickly get to the correct page without stumbling around.

• S03-Landing – Landing page from URL only for connection variability testing. This may be the page that comes with the web container (IIS, Apache, Jetty, etc.).

• S04-Home_page for the page that appears when the application is invoked. Appearance of this page indication that the application is “alive”, and can deliver resources. This page can be used for connection load testing.

• S05-SiteMap – lists all the pages on your website.

• S10-Sign-up to build user database build timing tests.

• S11-Log-in for authentication load testing.

  PROTIP: This is often the slowest transaction because authentication involves use of other services.

• S12-Menu traversal for variety and to ensure menus can be invoked in order to reach functionality to be load tested.

• S13-Add for app transaction DB build timings.

• S14-Updates for app user variety.

• S15-Report for app user mix load testing.

• S16-Deletes needed for emulating real work patterns during longitudinal/soak load test.

• There are additional ones such as pure API access.

---