Ways to Apply
Test Transactions are an essential part of the implementation process. Testing your configurations helps you gain an understanding of what your public Users will see during their checkout process.
Testing verifies that:
Items display correctly
Pricing is accurate
Prompts collect expected information
Payments process correctly
Receipts generate properly with important information
Catch other potential errors in the checkout process
Video Lesson
To learn more, please watch our instructional video about Testing Transactions in the Catalog Tab. Once finished, review how you can apply what you learned in the system before continuing to the next lesson, The Facility Calendar and Scheduler.
Need Help?
View answers to questions frequently asked by users in our Frequently Asked Questions or contact your CivicPlus representative if you have additional questions. Alternatively, you can review Tasks to Complete to see tasks that you can implement in your system on your own as well as Best Practice suggestions for implementation of testing reservations in the catalog.
Frequently Asked Questions
Should we test as Staff or as a Customer?
Both. A good best practice is to test from both the staff and customer perspective.
Staff Testing Verifies:
Administrative processes
Account management
Reporting
Customer Testing Verifies:
Public registration experience
Checkout flow
Self-service reservations
What should I look for?
The rate is correct for the time reserved.
Every add-on and deposit appears, with the right amounts.
Prompts display, and prompt-driven fees add correctly.
Waivers display and can be completed.
Pay later dates and amounts split as you expect.
The receipt shows the right header, footer, notes and answers.
The permit generates if you use permits.
When should testing occur?
When to Test:
During Configuration
After core setup is complete.
After Major Configuration Changes
Examples:
New discounts
New rate structures
Updated memberships
Before Go-Live
Final testing before opening registration.
After Significant System Changes
Verify expected behavior remains intact.
Tasks to Complete
These tasks give you hands-on practice with testing transactions in your own Recreation Management system, so you can see how it behaves before your customers do. You don’t need to complete every task. As you go, note any questions and bring them to your CivicPlus representative.
Catalog Testing Tasks
Create a test account (for example, last name Test or Fake).
Finish building the facility, including rates, prompts, waivers and add-ons.
Know your expected totals.
Make a reservation and review the cart.
Answer prompts, including any that add a fee.
Choose a paper waiver and confirm.
Take cash payment in full, then test pay later.
Check the receipt and permit.
Make the same reservation with a public test account.
Confirm the digital waiver pop-up works.
Confirm restrictions, approvals and add-ons behave.
Retest after any fee, prompt or waiver change.
Practice with staff before go-live.
Best Practices
Please consider some of our suggestions for applying best practices in the Recreation Management software. It is essential to evaluate your current processes and identify areas where improvements can be made. By doing so, you will not only streamline your workflow, but also provide a better experience for both staff members and public users.
Best Practice Recommendations
Use these recommendations to evaluate your current processes and find where small changes can make this feature easier for your team and your customers. They are suggestions, not requirements, so adopt the ones that fit your organization, and build the habits early, before the system is in daily use.
Use cash and a test account
Choose paper waivers during tests
Test every facility and session you build
Test pay later
Test publicly too
Use notes for later reports
Practice with your staff
Retest after changes
Review the receipt carefully
Note which receipts are tests
Recommended Launch Checklist
Use this checklist as a final review before your team and your customers start relying on this feature, to confirm nothing has been missed. It’s a last check, not a setup guide, so if an item isn’t complete yet, return to the tasks and best practices above before you launch.
Build multiple test accounts to test various scenarios
Test all rentable facilities
Test public and staff workflows
Review and build needed reports
Retest after major changes or updates
Initial Missteps
Please review initial missteps that are common with transaction testing to avoid issues when the feature is used. Please keep track of any questions you may have so your CivicPlus representative may address them.
Mistake | What Happens | Do This Instead |
|---|---|---|
Testing only internally | Public behavior may differ. | Test with a public test account too. |
Using real customer accounts | Real people receive emails. | Use test accounts. |
Making up card or check numbers for tests | You have to invent details. | Use cash. |
Choosing email waivers in tests | You get emails. | Use paper waivers. |
Not testing pay later | Dates or amounts are wrong. | Test a pay later transaction. |
Assuming paper waiver dates match reality | The system records the confirm time. | Know the date may differ from the paper copy. |
Testing once and moving on | Changes break things. | Retest after each change. |