All Fundraising components should be fully mockable and publicly testable. No test should contact a payment processor (test fixtures include sample API conversations).
We should run staging services on labs boxen, with realistic quantities of random data, protected only by minimal access restrictions to prevent complete pwnage (a la MediaWiki: namespace protection).
The staging environments should be provisioned using puppet modules which are available in both Labs and MW-Vagrant.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T88657 Fundraising Tech Staging (tracking) | |||
| Duplicate | None | T88012 Make credible dummy data set for fundraising CiviCRM testing | |||
| Declined | None | T88658 Write puppet (for vagrant) modules to provision all fundraising components | |||
| Resolved | • cwdent | T99869 create vagrant role for fundraising dash | |||
| Resolved | awight | T99951 Write puppet to provision DonationInterface | |||
| Invalid | Jgreen | T136963 overhaul payments-wiki deployment process | |||
| Restricted Task | |||||
| Declined | Spike | None | T130658 Spike: decide how payments-wiki deployment process should relate to the core MW deployment process | ||
| Invalid | Jgreen | T97745 Adjustable load balancer to direct small samples of donors to staging payments | |||
| Resolved | Spike | Jgreen | T112857 Spike: How to configure a staging server for payments? | ||
| Resolved | Jgreen | T136966 evaluate scap3 as a possible replacement for FrDeploy tools | |||
| Restricted Task |
Setting as resolved, the sub-tasks are either done or declined. Any future work would be re-scoped.