I'm currently testing a social/professional networking website. We are currently supporting RPC type urls (www.people.com/people.jsf?id=12234). In the coming release the application will support REST type urls (only for profile page, the rest of the application will remain unchanged). but we will still keep supporting the earlier type. I have been asked to come up with a elaborate set of cases to test this
The requirement are the following
1)Both type of urls should be supported
2)All profile pages must be accessible using REST type urls.
What kind of test cases can i create for this? The obvious ones are
1)cases that check that any particular profile is accessible using either form of URL.
2)Manually building urls by looking up the ref id from DB
Can you think of any other?
Ignoring algorithms, fancy diagrams, and all the technical details, REST simply consists of HTTP GET and POST requests to a web server which returns an HTTP response with data or content in whatever format desired (plain text, HTML, XML, JSON, binary, etc.)
Basically testing a REST application or web service is as easy as typing in URLs in a web browser (for HTTP GET related REST requests). If you do REST POST requests, you'll need to create a web form that sends POST requests or use a test tool instead of a browser.
REST is a simpler alternative (at least in making requests and offering more freedom or simplicity in how response is formatted) in that you don't need XML and all that crap that SOAP and XML-RPC requires.
In terms of URLs, REST, and RPC as you mention are exactly the same. The difference is in how the content may be returned and how the request is made. Can you make the RPC requests simply by typing in the URL in a browser?
So in a nutshell testing REST on a basic level simply requires knowledge of HTTP GET, HTTP POST, and HTTP responses, with knowledge of XML and JSON being helpful as well.