web based rss feed reader

A web based rss feed parser that has the same functionalities as google reader. The looks of the application must match the looks of the google reader at the time of the submission of this project. For this puprose a 3 days milestone is defined as follows : take screen shots of the google reader interface covering all the functionalities described in the attached specifications. If the looks of the google reader service changes at a later time, the coder is not bound to adapt the deliverable. The shots will be added to the [login to view URL] wiki with a reference to the corresponding statechart. Part of the work is to define a REST API for the backend service needed. This API will be delivered as self contained JS mockups used by the application. These mockups must be defined with the backend implementation in mind and the correspondance with REST calls returning JSON data must be precisely documented. Google Reader is a Google web application that allows the user to aggregate entries to sites using feeds. The Reader allows a user to subscribe to these feeds and catalogs them for the user. The Reader then displays the information in a useful manner to the user, and records how the user accesses and utilizes the information. Full specifications can be found at [login to view URL] and attached to this bid request. ## Deliverables S1) Complete and precise implementation of the description of the bid request. S2) Complete and fully-functional working web site(s) with no absolute URL in it. S3) Buyer will receive exclusive and complete copyrights to all work purchased. Third party software may be included as long as they are published under a license compatible with the GNU GPL. S4) Software must be browser and os independent. ---------------------------------------------------------------------- W1) A set of selenium ( [login to view URL] ) tests files containing all the URLs involved in the bid request. W2) All the selenium must be run in sequence with success, even if it implies to login into a service, meaning a login specific to the tests has to be created. W3) The normal user interactions expected at a given URL must be tested with a selenium test or unit test. Each user action must be tested in a separate test. The test must fail if the user interaction does not produce the expected result. W4) All javascript functions must be tested using [login to view URL] and reach 100% coverage. All code must be encapsulated in functions. All javascript functions must be defined in .js files. ## Platform Web Browsers IE and Firefox in particular