Skip to content
This repository was archived by the owner on Jun 20, 2018. It is now read-only.

Test users support in the API #64

Open
andreskytt opened this issue May 12, 2016 · 1 comment
Open

Test users support in the API #64

andreskytt opened this issue May 12, 2016 · 1 comment
Assignees

Comments

@andreskytt
Copy link
Contributor

As a developer, I want to be able to explicitly tell the API that what I am doing now is for testing purposes and should follow a different path of business logic. By default, that path is probably "have no consequence whatsoever" but more complex interactions might, for example, redirect the calls to different instances running on a separate test environment

@andreskytt
Copy link
Contributor Author

As a sysadmin I want to be able to flick the API between three different modes:

  • Record. The (selected)inputs are hashed and the entire response is stored along with that hash
  • Playback. If the input hash matches one of the recorded responses, the recorded response is played back without any business logic being executed
  • Normal. Neither playback nor recording happens

@peterjasc peterjasc self-assigned this Jul 31, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants