Transaction Monitoring (Web Application Monitoring) can save brand reputation and revenue by capturing issues with your transactions. Transaction Monitoring is a synthetic monitoring approach where Uptrends' checkpoints follow a script to simulate real user journeys. When setting up user journey tests, it is important to think about short and long-term ramifications of your testing. You can avoid many problems by carefully mapping out your transaction before recording. Every use case is different, but we found some common problems you may want to think about when setting up your Transaction Monitoring.

Avoid Inventory Shortages

Inventory shortages due to testing shopping carts and checkout transactions can cause problems with your inventory. The synthetic testing places orders as frequently as 288 times a day, and if not handled properly, testing can reduce your inventory making the item unavailable to your users. We've actually seen problems where the warehouse processed and readied the orders for shipping.  We’ve seen several different solutions to avoid inventory problems.

Database solution

Although we’ve seen some companies choose to delete test purchases and shopping carts from the database manually, a stored procedure or automated process may prove more reliable.

Use test (virtual) items

You may find it beneficial to create an inventory item that is used strictly for testing purposes. Using a test item keeps your actual inventory accurate and available. Test items may also help you identify test transactions when purging your databases and prevent accidental shipping of actual items.

Dump the cart

If testing a shopping cart transaction, build item removal into the transaction steps. Add an item and then remove the item before closing the transaction.

Pick an item with large quantities

If using a real item, pick an item for testing with such large quantities that an inventory shortage becomes nearly impossible.

Avoid filling up appointments and reservations

If your transaction monitor tests schedulers for things like doctor appointments, hotel rooms, flights, or dinner reservations, you can quickly find all of your time slots full or sold out. Identifying and purging appointments created by testing is crucial.

Your transaction monitor WILL send emails

If part of your transaction includes an email field, and your transaction sends confirmation emails for any reason such as invoices, password resets, or user ID reminders, your transaction monitor will also generate emails. To avoid a mailbox full of unwanted emails, use an email address such as a noreply@mysite.com for your transaction monitor. 

Unexpected credit card charges

If you use a real credit card when testing the checkout processes, you can accrue charges and merchant fees, get holds placed on the available funds, and trigger fraud alerts due to the frequent transactions. Instead, use test credit card accounts. Most merchant service companies offer test account numbers that allow you to test the checkout transaction without assessing fees or putting holds on a real account.

New account creation solutions

When testing new account setup, you can only do it once with the same username. The second time the script runs the transaction will error due to the duplicate account. We’ve seen a few solutions for testing account setup.

Don't commit the data

Although this option doesn’t provide a complete test of the entire account setup, some Uptrends users have chosen to stop short of the final commit. The monitor tests every aspect of the account creation process except the final submit.

Database solutions

You may want to consider using a database trigger to check for the test account id after a CREATE event that purges the test account from the database before the next test begins.

Generate new unique logins

You can also generate new unique logins by using things like the time date stamp. Just remember to purge them on a regular basis. Check with support to learn more.

Account already logged in

If using the same login credentials for multiple monitors or you fail to log out after a test, you may generate errors. Best practice is to set up a different test user account for each monitor, and always log out as the final step in the test process to avoid unnecessary alerts. To add a content check, before triggering the next step, switch to the other browser window (usually behind the window your using for recording).

Use content checks

Content checks are free, and you can add one to each step in your transaction. Content checks are a great way to make certain the page loaded completely and that the browser received the correct content. You add content checks during the recording process before you begin the next step. To make a content check:

  1. Locate the Recorder browser window usually behind the active recording window.
  2. Click the +Add content check button.
  3. Add the text for the content check.
  4. Click Save.
Note: Every use case is different so don't hesitate to reach out to our scriptwriters to help you find solutions that fit your unique situations. Either use the ticket system or include a note on your transaction recording submission to let the writers know about any concerns.