| Issue 194: | API Sandbox / Testing Mode | |
| 14 people starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
As raised: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c30777572755d0a Currently it is difficult to unit test a twitter client or interface, as the expected response received are heavily reliant on the current state of the authenticated user. Additionally, rate limiting and the difficulty of creating/deleting 'test' friendships/notifications/blocks etc make it a largely manual process. This request is for a 'sandbox' api or 'testing mode' flag. It would: * Validate requests for each API call, returning the expected success or failure notice for each request. * Not be rate limited * Return sample testing datasets of a known form to each request. * Have no effect on live data This would be extremely useful for creating unit testing frameworks for twitter libraries. Possibly also useful for Twitter staff for identifying bugs :) Thanks, Hamish Campbell |
||||||||||
,
Dec 12, 2008
Issue 196 has been merged into this issue. |
|||||||||||
,
Dec 12, 2008
(No comment was entered for this change.)
Labels: -Type-Defect Type-Enhancement
|
|||||||||||
,
Dec 15, 2008
(No comment was entered for this change.)
Status: Accepted
Labels: -Priority-Medium Priority-Low Milestone-V2 |
|||||||||||
,
Jan 20, 2009
Would love this! Every new coder that works on a Twitter project with us wants a sandbox. |
|||||||||||
,
Apr 20, 2009
(No comment was entered for this change.)
Owner: alexfpayne
|
|||||||||||
,
Apr 21, 2009
This issue has been recoreded in the future roadmap: http://apiwiki.twitter.com/V2-Roadmap
Status: Moved
|
|||||||||||
,
Apr 21, 2009
Marking "Invalid" so these issues don't clutter the main view of issues. All are tracked on http://apiwiki.twitter.com/V2-Roadmap
Status: Invalid
|
|||||||||||
|
|
|||||||||||