What’s the best way to test the entire system from registration to final email and payment?
I put a test ticket ($1) on my event and registered myself, which was fine as I received all emails and saw all the pages. But I can’t easily remove those registrations and can’t remove the test ticket from the event (because of the registration).
Am I best off to create an entirely fake event for testing and then delete it when I’m done? How do you recommend we test the system and all its possible scenarios?
I would model a test event after a live event by using the duplicate button in the event editor (appears under event title). Then you could adjust the pricing for a ticket to a lower value such as $1 and then save changes.
Afterwards, you could un-publish the event.
If you would like to remove the test registration as associated information then you can do so with these steps:
1) Go to transaction details screen and delete the payment.
2) Go to registration and trash it. Then permanently delete it.
3) Go to test event and trash it and permanently delete it.
You’ll need to complete the steps in the above order. Otherwise, you’ll see notices to remove existing information before attempting to delete.
—
Lorenzo
Viewing 1 reply thread
The support post ‘How to test the system’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
Support forum for Event Espresso 3 and Event Espresso 4.