background preloader

Testing Backbone applications with Jasmine and Sinon – Part 1 – Tinned Fruit

Testing Backbone applications with Jasmine and Sinon – Part 1 – Tinned Fruit
Overview This is the first in a series of articles demonstrating how to test a Backbone.js application, employing the Jasmine BDD test framework and the Sinon.JS spying, stubbing and mocking library. In this part, we’ll take a brief look at Backbone, and then move on to an introduction to some of the features of Jasmine and Sinon.JS. If you have never written any JavaScript tests before, you might like to take a look at Christian Johansen’s recent series of articles over at scriptjunkie. Backbone everywhere In the last few months, Backbone.js has received a fair bit of exposure, with a number of tutorials and one or two high profile implementations. Backbone’s popularity is understandable. Backbone’s MVC structure lends itself very nicely to bottom-up unit testing. This should be very familiar to anyone who has spent any time testing applications developed with MVC frameworks such as Rails or Django. About Jasmine BDD BDD emphasises shared language amongst developers and stakeholders. Specs

Understanding Web Security Using web.xml Via Use Cases We Recommend These Resources The deployment descriptor, web.xml is the most important Java EE configuration piece of Java EE Web applications. The security configuration in this descriptor drives the semantics and operation of web container security. Hence it is very critical that web developers and administrators understand the various combinations possible in the security configuration in this descriptor. Security Constraints Security Constraints are least understood by web developers, even though they are critical for the security of Java EE Web applications. In this section, we will look at specifying the security constraints for multiple use cases. Use Case: We would like to define a set of web resources that will have unchecked access. 01. 02. 03. 04. 05. 06. 07. 08. 09. 10. 11. 12. 13. 14. 15. 16. Use Case: HTTP GET operation on a set of web resources should be accessible only by an user with the role "Employee". 02. 03. 04. 05. 06. 07. 08. 09. 10. 11. 12. 13. 14. 02. 04. 05. 06. 07.

Datavisualization.ch Selected Tools

Related: