All Collections
Basics - Which features to test? How to test a web shop?
Basics - Which features to test? How to test a web shop?

What should you test first and how to test an entire web application such as a web shop?

Arto Vuori avatar
Written by Arto Vuori
Updated over a week ago

Eliminate repetitive testing, release faster

This post is our guide which top features to test, and how you can get the benefits of automated testing with minimum work. You don’t even need a dedicated test server, your laptop is enough. By adjusting this how-to to your needs, you can have your web project under automated testing in 45 minutes without the need to change your software or setup any additional servers.

Which features to test?

  1. Test how to create a user. This is generally one of the first steps of any web based service.

  2. Test how are the user’s first moments and how he/she is guided through your product and its features.

  3. Test that your sign in works. The user cannot access your product without a properly functioning log in.

  4. Secure your revenues by testing payment features, e.g. credit card purchases

  5. Test the most valid features for your product. This can be sending messages, if the product is heavily based on communication. Alternatively, a crucial feature for your product could be searching items in a web shop or adding them to a shopping cart.

Set up a connection to test your app

If you have a web server which can be access from the internet you can skip this section.

When all your servers are in private networks or you only have your laptop computer, you can create a tunnel for your web app to enable Usetrace test it. To make private web server accessible from the internet see how to create a Tunneled connection. Remember to copy the public URL to be used later as the default base URL in Usetrace.

Set up your Usetrace account

Sign up

If you don’t already have a Usetrace account, sign up at

Set the default base URL

When you are logged in after signing up you will be asked for the base URL. Insert your web servers public URL as default base URL in Usetrace.

How to test a web shop?

Keep in mind that your product might differ a lot from the examples. Not everything fits all and there may be need for some adjustments specially for the features to test. Here are steps to help you test your web shop:

Create a test trace for signing in

  1. Continue by adding something to the shopping cart

  2. Finish the trace by buying the product

  3. Name your trace with “Log in + Add to cart + Buy”

Split your trace to reuse its parts later on

  1. Extract the trace into distinct use cases: log in, add to cart, and buying:

Note! When extracting steps to create a new trace, a window will ask you for the name of the new trace. Give a meaningful name for the extracted use cases, e.g. ”Add to cart” or “Log in”.

Create another trace to test signing up as a new user

  1. Start by selecting ‘New Trace’. Check out the tutorial for registering as a user (verification with e-mail):

  2. Go through the steps the user faces the first time when logged in, e.g. filling user profile details

  3. Add the previously created routines (Add to cart, Buy) by adding routine steps into the trace you have now open in the Editor:

  4. Name your trace with “Register + Fill User Profile + Add to cart + Buy”

Now you have created traces, which test the most prominent features with respect to your product. Now exit Editor.

See the results and get regular reports

  1. Set up the reporting to get feedback from your test runs to your chat or email (

  2. Set the reporting to “always”.

  3. To receive reports, you must have Pro or Enterprise Plan. Hit the upgrade button when inside Usetrace to upgrade

  4. Launch your testing every time you have finished an improvement for your product by clicking ‘Run All Traces’ on the Usetrace Dashboard.

  5. Check the status of your product from the feedback report

Note: You won’t receive reports when running your traces in the Editor. The reports will be sent when the test batch finishes after hitting the ‘Run All Traces’ button inside Usetrace, or via “Settings > Scheduling & Reporting > Scheduled run” or automation integrations like Jenkins

You’re all set

You have now set up testing for your most critical use cases and Usetrace cloud does the testing for you. You are ready to develop new features and release them quickly while you can be 100% sure those critical features are covered automatically by the tests you just defined.

Did this answer your question?