![]() In this case, it’s best to break up the single “Assign” step into individual “Keypress” steps to key in the values one digit at a time. If you find that the credit card information is being jumbled when it is assigned during the test run, that typically means that the assignment is happening too quickly and is conflicting with Stripe’s validation logic. Ghost Inspector will still be able to locate the elements and will continue to work even if the iframe’s name attribute changes. In most cases, you can broaden these selectors by changing the iframe portion to simply iframe. However, the _privateStripeFrame8 that is used in the name attribute of the iframe could potentially change. These steps should work properly from the get go in your test. ![]() If you’ve used the test recorder to capture your actions during a Stripe checkout, you should see a set of steps similar to the ones shown below. However, due to the form validation involved and the dynamic attribute tags, small tweaks may sometimes need to be applied after your test has been recorded. Ghost Inspector is fully capable of testing checkout flows that use this payment module. They offer various ways of capturing payments, one of which is a drop-in JavaScript + iFrame checkout module for your website. Stripe is a common payment platform used across the web. Live credit card numbers should not be used in your Ghost Inspector tests. This typically means using a card number of “4242 4242 4242 4242”. ![]() Stripe Checkout should always be tested in “Test” mode using dummy information.
0 Comments
Leave a Reply. |