Devlopment tales

The development of Angular 2 is on its way with much talk, hype, and fanfare. Surprisingly, there is not much being said about unit testing. As a responsible developer, you have undoubtedly already written a giant unit test suite to achieve ‘near perfect’ code coverage, and I'm here to let you know, there is no need to throw that all away! While Angular 2 is currently in ‘developer preview’, implying that nothing serious should be built with it currently, the Angular Team has already created a giant wealth of unit tests and a custom testing setup: (https://github.com/angular/angular/tree/master/modules/angular2/test). Unfortunately, it is not easy to set this up for yourself. So this post should help you get started. link to full post here

Firstly, what are Page Objects? Here is a definition from the Selenium team: Page Object is a Design Pattern which has become popular in test automation for enhancing test maintenance and reducing code duplication. A page object is an object-oriented class that serves as an interface to a page of your AUT. The tests then use the methods of this page object class whenever they need to interact with that page of the UI. The benefit is that if the UI changes for the page, the tests themselves don’t need to change, only the code within the page object needs to change. Subsequently all changes to support that new UI are located in one place. Using Page objects in test cases has been very useful. It will feel hard and time consuming initially but, once you have all page objects up and running. Its going be a smooth ride . Till now writing test cases for an Angular Apps has been smooth ride. Thanks to some good articles online to get me going. I have found some very helpful resour...

Lately, I have been working on setting up the testing framework and writing test cases for angular apps. I am using Karma-Jasmine framework for unit testing. And for end-to-end testing, am using another testing framework called Protractor. I like to follow best practices while using any technology. It will feel hard initially but, you will find the its usefulness as you come across complex scenarios. Till now writing test cases for an Angular Apps has been smooth ride. Thanks to some good articles online to get me going. I have found some very helpful resources, which talks about unit testing and end-to-end testing which, I would like to share with other peps... Enjoy.. Unit testing AngularJS applications AngularJS: Developer Guide: Unit Testing Using Protractor: Writing end-to-end tests has never been so fun. Protractor - end to end testing for AngularJS

ECMAScript 6 is the upcoming version of the ECMAScript standard. This standard is targeting ratification in June 2015. ES2015 is a significant update to the language, and the first update to the language since ES5 was standardized in 2009. Implementation of these features in major JavaScript engines is underway now. Click here to read more about .. ECMAScript 6 Features

This slide will review various common smelly snippets of code and discuss techniques on how we can eliminate and protect against their pungent odors. JavaScript Code Smells

I came across an interesting article on AngularJS internals authored by Nicolas Bevacqua . This article gives a very clear understanding of the entire idea of scoping! AngularJS presents a remarkable number of interesting design choices in its code base. Two particularly interesting cases are the way in which scopes work and how directives behave. The first thing anyone is taught when approaching AngularJS for the first time is that directives are meant to interact with the DOM, or whatever manipulates the DOM for you, such as jQuery ( get over jQuery already !). What immediately becomes (and remains) confusing for most, though, is the interaction between scopes, directives and controllers . Read more...

When looking at the existing JavaScript solutions for building native iOS and Android apps, it's a fact that they're powerful and can extremely reduce the amount of application development time. On the other side it's also clear that they come with drawbacks and limitations. It depends heavily on a project's requirements and of course on the developer skills and sensibilities. App performance and UI responsiveness are the main aspects when it comes to the question of using a JavaScript solution or not (native apps with a single C# code base can be realized with Xamarin). It should be clear that WebView wrapper approaches will never reach native-quality UI performance. So developers should start with a proof of concept when choosing a HTML-based WebView solution: mastering dynamic data and optimizing form controls are non-trivial tasks. The Mobile App Framework Matrix represents a comparison and documentation of current technologies for building native iOS and A...