Fake Response Server: Slow response time generator

Here is another quick tool built on GAE AWS. This one is super simple, but pretty handy. Today Twitter went down, and somewhere in our system we were using the Twitter API to display one of our status feeds. Them being down became us being slow.

Well, I wanted to do some quick tests to keep this from happening again, but byt the time I got to it Twitter was responsive again. To fix it I would need to create a bad URL. The crappy thing is I wanted a slow response time, not exactly a bad response/error. Creating a 404 error is easy, just go to some url that doesn’t exists and test. But I want a slowwwww response.

I quickly searched Google for something I could use, and didn’t find one. When I realized I would have to create a fake pause endpioint somewhere I figured someone else out there might benfiift from a quick public version of this system. So, I created fake response server. The first default endpoint available sleeps for a variable time.

fake-response.appspot.com (Update: Moved to AWS)


and add a sleep param to change the sleep time in milliseconds

fake-response.appspot.com?sleep=5 (Update: Moved to AWS)


Nothing major, but why not publicize the tool incase it can help some other shmuck out there like me 🙂


Release Notes Generator (For Pivotal Tracker)

Here is another quick tool built on GAE. It takes all your PT stories and bugs, scrapes out chores, and release stories, leaving a listof features and bugs available to copy and paste in to your release notes, emailer, or README file.

Often departments always asking if a release is out, what features are included, and if it is not out how long until it is. This tool will also print a header letting the person using the tool know if the release in question is out, and if not how far down the pipeline it is.

To use the tool most effectively you should check out my post on releasing versions through PT. (coming soon)

Download RNG for PT

Or fork and contribute on GitHub