Page MenuHomePhabricator

In the event that credentials for a gateway are not supplied, that gateway should go in to local development mode.
Open, HighPublic


Currently, a paymentswiki instance with empty configuration will not work properly, and cannot make requests to the payment processors.

We want to fall back to a mode which does not require credentials, and does not make internet connections. This will make it possible to do any sort of testing of multi-step donation workflows.


  • It should be inescapably obvious to the user, whenever they are in local dev mode… but not in such an extreme way that we couldn’t use this technique to finally allow selenium tests to be possible.
  • In local dev mode, there will be no attempts to actually contact third parties. Ideally, this would be rendered impossible within all gateways in local dev mode.
  • Short-circuit all FormChooser safety checks, for any gateway in local dev mode.
  • All 3rd party responses and workflows will be faked when we are in local dev mode.
  • When a gateway takes you to a piece of the workflow hosted by a 3rd party, local dev mode will allow the user to supply the values for expected parameters that they would like to be pretending to receive from the 3rd party.
  • For all gateways, if the user is typically sent away to a third party and expected to return, it should always be possible in local dev mode to get 100% of the way to the Thank You or Error page by very thoroughly faking the external bits, internally.

Event Timeline

awight assigned this task to K4-713.
awight raised the priority of this task from to High.
awight updated the task description. (Show Details)
awight set Security to None.

Did someone work on this project during Wikimedia-Hackathon-2015? If so, please update the task with the results. If not, please remove the label.

I did, yes. But I was not able to get the patch I was working on, to a place where I could commit something mergeable before I left.
This task should probably be broken down a bit before we take another swipe at it.

We are trying to help all open tasks listed under "Work continues after Lyon" at the Wikimedia Hackathon 2015 workboard finding their best way forward. * If you are participating in Wikimania, consider adding the #Wikimania-Hackathon-2015 project to get this task in that loop, which is about to start. * If you think this project could welcome help from a dedicated Google Summer of Code or Outreachy intern, or from an Individual Engagement Grant, add the Possible-Tech-Projects project. * If you would like to receive some other type of support (organizing a Tech Talk, establishing contacts with existing developer teams in Wikimedia or elsewhere, travel sponsorship for a related activity... you name it), please create a subtask explaining your request and associate it with Developer-Advocacy (or you can start by commenting here if you prefer). * Keeping the description, priority and assigned fields up to date always helps. :) For some context about this message, see T101151: Evaluate which projects showcased at the Wikimedia Hackathon should be supported further. It is the last communication related to Wikimedia-Hackathon-2015 that we will post here.

Aklapper added a subscriber: K4-713.

@K4-713: Resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!).
Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task.
Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - thanks!