| 1 | Transaction goes through and Sue confirms it | Al,Sue | ASAP | Al? makes a transaction, Sue confirms receipt |
| 2 | Post-transaction screen deemed acceptable (and if we have to make one, we make it) | Al, Stephen | ASAP (before sue's vacation) | Al? makes a transaction, livestreams or screenshots result |
| 3 | Ensure that QR codes behave as expected when scanned with wallet app | Al?, Stephen | ASAP | Someone with a wallet app should scan each QR code and ensure that the correct crypto address for the correct cryptocurrency is populated in the app, in whichever manner is expected - this should not require us to further ensure that the wallet app itself acts as intended, unless that is desired |
### Tor staff / naive user credit card tests
| # | What are we proving | Who's Testing? | Start when? | How are we proving it |
| 4 | Ensure gift card credit card transactions are successful - this is a site navigation / design test | Tor staff, | 27 August | Make payment with gift card; take screenshot(s) of final result OR anything that looks out of place, noting OS and browser; record transactions in google sheet - MATT WRITES INSTUCTIONS |
| 5 | Test PayPal interface using naive users and dummy PayPal info | Tor staff | 27 August | take screenshots as above, noting OS and browser |
| 5.5 | Check these transactions against staging CiviCRM | Matt | 27 August | |
### CiviCRM recording
| # | What are we proving | Who's Testing? | Start when? | How are we proving it |
| 6 | Ensure credit card one-time payments are tracked | Matt, Stephen | ~27 August | Make payment with for-testing CC# and conspicuous donor name, then check donation list in CiviCRM |
| 6.5 | Ensure credit card transaction against live card operates as expected | Matt, Stephen | ~27 August | If changes don't need to be made to live settings to accomplish: Make payment with ML's CC, check donation list in CiviCRM, check Stripe |
| 7 | Ensure credit card errors are not tracked | Matt, Stephen | ~27 August | Make payment with for-testing intentionally-error-throwing CC# (4000 0000 0000 0002) and ensure CiviCRM does not receive data. Ideally, ensure event is logged |
| 8 | Ensure Paypal one-time payments are tracked | Matt, Stephen | ~27 August | Make payment with Paypal account, then check donation list in CiviCRM |
| 8.5 | Ensure Paypal transaction against live account is tracked | Matt, Stephen | ~27 August | If changes don't need to be made to live settings to accomplish: Make payment with ML's account, check donation list in CiviCRM, check Paypal |
| 9 | Ensure Stripe webhooks catch behavior properly | Matt, Stephen | ~27 August | Use Stripe webhook testing tools to generate events and test output - may involve changing webhook endpoint in Stripe backend to donate-neo staging |
| 10 | Ensure Paypal webhooks catch behavior properly | Matt, Stephen | ~27 August | Use Paypal webhook testing tools to generate events and test output - may involve changing webhook endpoint in Paypal backend to donate-neo staging |
### GENERAL SITE TESTS
| # | What are we proving | Who's Testing? | Start when? | How are we proving it |
| 12 | Test standalone subscription form | Matt, Stephen | ~27 August | CiviCRM receives intent to subscribe and generates - and sends - a confirmation email |
| 13 | Test confirmation email link | Matt, Stephen | ~27 August | Donate-staging should show a success/thank-you page; user should be registered as newsletter subscriber in CiviCRM |
| 14 | Test "newsletter actions" | Matt, Stephen | ~27 August | Should be able to unsub/resub/cancel sub from bespoke endpoints & have change in status reflected in subscriber status in CiviCRM |
| 15 | Test donation form subscription checkbox | Matt, Stephen | ~27 August | Should generate and send confirmation email just like standalone form |
