#rylan-testing

1 messages · Page 1 of 1 (latest)

final crest
#

hi there! no we don't have a ready made testing suite that will test every possible user interaction and tell you which test(s) failed.

You'll need to build your own test suite for unit testing or functional testing.

loud wren
#

So my best approach is just to launch the Stripe integration and hope that my testing was sufficient?

#

Honestly, that's a daunting notion

#

What happens if a bunch of people sign up and I somehow screw up all their payment info?

final crest
#

you can do a single low value payment after launching to see if everything works in production i.e. what some people call a penny test

loud wren
#

I can only test in the ways that I know how

#

I guess your point is just to charge so little that people won't care?

#

Ok let me maybe ask a related question

#

During a checkout session

#

My webhook gets hit with the following sequence of events:

#

charge.succeeded -> payment_method.attached -> customer.created -> customer.updated -> invoice.created -> ... -> checkout.session.completed

#

In that entire chain, what information do I want to make sure I'm logging or writing to my database?

#

i.e. what information is critical for me to later have access to?

final crest
#

I guess your point is just to charge so little that people won't care?

that's not what i mean by penny test. A penny test is a test done by you (the merchant) with a very low amount to ensure everything is working as expected

loud wren
#

Oh, I'm not worried about the proper payment flow not working. I don't expect a problem with that

#

I'm worried about a user accidentally getting caught in a payment loop

#

Or a user accidentally checking out 5 times

#

i.e. unintentional user behavior that would result in my users have a negative experience

#

Or something else crazier