Jobs is giving his keynote, introducing the next generation of iPods, iTunes and Apple TV. One of the things I like, probably everybody likes, about Apple is their continual innovation. One takeaway from the keynote is Jobs' description of the driving factor behind Apple's innovation and success:
We listened to what customers wanted... This is what customers were telling us... Our customers wanted this.
This extension provides goto, gotoIf and while loop functionality in Selenium IDE. Selenium IDE is a plugin for Firefox that automates the testing of web-based applications. There is an excellent flow-control extension at wiki.openqa.org/display/SEL/flowControl for the Selenium RC and TestRunner components, but it does not work with Selenium IDE (the Firefox plugin) directly. This makes it difficult to develop controlled test cases within Selenium IDE, and there are times when the frame-based TestRunner cannot be used (such as when the website under test employs a frame-buster script).
I've ported the existing control-flow extension to work in the Selenium IDE Firefox add-on. The image below shows a sample test case using goto, gotoIf and a while loop, all running successfully in Selenium IDE.
The file can be downloaded from Github and should be saved as "sideflow.js" to your hard drive. Then the Options settings in Selenium …
In Rest, collections and resources are accessed via HTTP URI's in a similar way:
members/ -- a collection of members members/1 -- a resource representing member #1 members/2 -- a resource representing member #2
It may help to think of a REST collection as a directory folder containing files, although its highly unlikely that the member data is stored as literal JSON files on the server. The member data should be coming from a database, but from the perspective of a REST API, it look…
REST purists insist that PATCH is the only "correct" way to perform partial updates , but it hasn't reached "best-practice" status just yet, for a number of reasons.
Pragmatists, on the other hand, are concerned with building mobile back-ends and APIs that simply work and are easy to use, even if that means using PUT to perform partial updates .
The problems with using PATCH for partial updates are manifold: Support for PATCH in browsers, servers and web application frameworks is not universal. IE8, PHP, Tomcat, django, and lots of other software has missing or flaky support for it. So depending on your technology stack and users, it might not even be a valid option for you.Using the PATCH method correctly requires clients to submit a document describing the differences between the new and original documents, like a diff file, rather th…