Testing Exhibitor Sign Up Flow End to End

Created by John Connolly, Modified on Thu, 11 Jun at 11:35 PM by John Connolly


SOP: Test the Exhibitor Sign-Up Flow Before Going Live


Objective


This SOP explains how to validate an exhibitor sign-up flow using both preview mode and the live end-user link. The goal is to confirm the registration form, package settings, pricing rules, and payment processing behave correctly before launch.

Key Steps

 

1. Review the sign-up flow in preview mode 0:01

  • Open the exhibitor sign-up flow using the Preview and Preview Sign-Up Flow options.

  • Use preview mode to quickly review: 

    • Overall flow and page sequence

    • Registration form layout

    • Field order and required fields

    • Package display and selection

    • Booth pricing rules

  • Move through each step as if you were an exhibitor to confirm the experience is logically structured.

 

2. Validate form fields, packages, and pricing rules 0:29

  • Check that all required registration fields appear correctly.

  • Confirm the fields are in the intended order.

  • Test required-field behavior to ensure validation messages appear when expected.

  • If packages are offered, verify: 

    • Package options display correctly

    • Quantity limits are enforced

    • Package availability matches your settings

  • If booth pricing rules are configured, confirm the correct pricing is applied during the flow.

 

3. Test payment processing with a real transaction 1:06

  • If credit card payment is enabled, create a low-cost test item such as a $1 add-on or $1 package.

  • Add the test item to the cart.

  • Proceed to checkout and enter a real credit card.

  • Complete the payment and verify: 

    • The transaction succeeds

    • The payment posts to the correct account

    • The amount charged matches the test amount

  • Use this step before launch to confirm payment handling works end to end.

 

4. Retrieve the live sign-up link from event setup 1:48

  • When you are ready to test the real end-user experience, go to Event Setup.

  • Locate the actual sign-up flow link at the top of the page.

  • Click the copy button to copy the URL.

  • Save the link for testing or send it to another tester if needed.

 

5. Test the live link as an end user 2:08

  • Because you are logged in as an admin, test the live link in a way that avoids admin session interference.

  • Use one of these methods: 

    • Log out of the admin account, or

    • Open an incognito/private browser window

  • Paste the copied URL into the new session.

  • Confirm the live flow loads correctly and matches what end users will see.

 

6. Compare live behavior against preview mode 2:35

  • Review the live flow carefully and compare it to preview mode.

  • Confirm the live experience behaves as expected for an actual exhibitor.

  • Verify that the pages, form behavior, and checkout process function correctly outside of preview mode.

  • Use this final check to ensure the sign-up flow is ready for launch.

Cautionary Notes

  • Preview mode is not fully identical to the live user experience. Some features may not behave exactly as they will for end users.

  • Do not rely on preview mode alone if you need to validate checkout or final user behavior.

  • Use a real card only when necessary and only with a low-value test amount such as $1.

  • Confirm the payment posts to the correct account before going live.

  • Avoid testing the live link while still logged in as an admin, since that can affect what you see.

Tips for Efficiency

  • Use preview mode during setup to quickly catch form, package, and pricing issues early.

  • Create a reusable $1 test item for fast payment verification.

  • Use an incognito window for live testing to avoid logging out and back in repeatedly.

  • Keep a checklist of required fields, package limits, pricing rules, and payment confirmation so each test is consistent.

  • Test the flow after every major configuration change to catch issues sooner.

Link to Loom

https://loom.com/share/c0b06c333a5340fe9cb62943b8e5675e

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article