%% Last Updated: - [[2021-04-19]] %% A User Path in [[Software Testing]] is a single flow of actions that a production user might take to accomplish a single task. In [[Load Testing]], this is often called a "scenario" (different from [[Test Scenarios]]). An example of a user path could be, for example, the actions that a user takes from landing on the home page to browsing a catalog of items for sale to actually adding the item to a cart and checking out. While this path actually exists in your application, one thing you might consider is alternative user paths. Perhaps instead of browsing, a user searches for a particular item, finds that it is out of stock, and signs up to be notified when the item is back in stock. It might be worth thinking about scripting a separate flow to account for users like this, depending on how common this situation may be. Including multiple user paths [[Making load testing scripts more realistic|makes load testing scripts more realistic]]. ## In [[Load Testing Tool]]s - [[Executors in k6]] - [[JMeter Thread Group]] - [[Scenarios in Gatling]]