JavaScript for Line of Business Applications

Many developers and development shops have embraced testing in their server side code – either using a TDD model, or sometimes just with unit or functional tests created on the fly – but very few developers I talk to test their front end code beyond eyeballing it in a few browsers (or if they’re lucky, with a service like BrowserStack). And even fewer of those use any kind of automation. In this post I’m going to try and help out that majority of you who aren’t testing – or maybe just aren’t automating.

Lately I’ve been converting a number of my jQuery plugins over to Github – something the new jQuery plugin site is requiring – and while doing so I’m refactoring and adding tests with QUnit(created by the same folks that write the jQuery core). I realized pretty quickly that having to go to the browser, hard refresh, and then run the tests again after every change was a time killer, but I didn’t want to write a whole bunch of tests and then go check the results, otherwise I could be tracking down bugs (in my code and the tests) for days. Instead I set up some automated testing using Grunt, PhantomJS, and a couple Grunt plugins. Here’s how.

I decided to dedicate this series to building a test-driven application that would allow me to create a Grocery List. I figured it will be a small enough application to not get muddled down in large, complex requirements and several moving parts but still provide a real-life example of a CRUD-based application.

A Grocery List application is also something I have wanted to make for some time. We still, as a household, create a grocery list with pen and paper and take it in hand to the store. Nothing wrong with that, aside from the general user error of a)forgetting the list at home, and the user experience oversight of b) not being able to split up and cover parts of the list as a group. So, I thought it may be handy to have a web-based application that my family could add to, remove from and have available on the one thing we never leave the house without: attitudes. No. smartphones.

* Part I – Introduction
* Part II – Feature: Add Item
* Part III – Feature: Mark-Off Item
* Part IV – Feature: List-Item-Controller
* Part V – Feature: List-Controller Refactoring
* Part VI – Back to Passing
* Part VII – Remove Item
* Part VIII – Bug Fixing
* Part IX – Persistence
* Part X – It Lives!

As technology changing rapidly many JavaScript libraries have become the new trend .Lots of JavaScript libraries are coming to internet to make web faster and user friendly .
So i am going with the time starting series of blogs for Knockout .Below you will find the knockout introduction presentation , i will describe each slide in details in upcoming blog post .

* What is Knockout and Why to use it ?

* Places to Learn ,Run and Test Knokout.js

This post is about how this unexpected behaviour led me into having a refresher of some of the core concepts regarding how JavaScript executes.


I and a colleague at work, were implementing a piece of functionality which basically translates to: "Create a function such that if that function is called with a delay flag being true, have a timeout for a line within the function, if not, then call that line immediately". Something like this...

Ok. Then it is obvious I've got something new to learn here. So I decide to dig more into why this is the case. A couple of researching got me the reason behind this behaviour. And to understand why things tie up this way, I needed to revisit what it meant by JavaScript being single threaded, non blocking I/O and has an asynchronous event queuing model for code execution.

Ruby on Rails MVC Is Not the Same as Ember.js MVC

One of the most confusing parts for people coming from Rails (or any other backend web application framework) it’s that what Ember.js calls MVC is very different to what other frameworks call MVC.

The following are the steps mention by Yehuda and the components in charge of each in both Ruby on Rails and Ember.js...

For the past few months I've been working on a project with a fairly complex interactive web interface. This required me to venture into the wild and unpredictable jungle of Javascript development. I was totally unprepared for what I would find. Soon after starting the project it became clear that just using JQuery would not be sufficient for my project. I needed a higher level Javascript framework. After a doing a little research I settled on Ember.js.

Ember was definitely a big improvement over straight JQuery, and allowed me to get some fairly complex UI behavior working very quickly. But recently I've run into some problems...

* Jasmine - a BDD framework that's clearly influenced by RSpec, and

* QUnit - a more traditional test framework from the jQuery project.

I compared them on three criteria:

1. Speed of setup. I tend to avoid testing tools that take me more than hour to get up and running.

2. Simplicity. Test frameworks don't need to be complicated; they just need to let me specify how my code should behave and keep out of my way. All things being equal, I'll choose an xUnit style testing framework to an RSpec style framework. If you're thinking "but I prefer BDD!" don't forget that the "B" in BDD is just language, and you can use that language in any framework you like.

3. Support for Continuous Integration. If you can't run your test suite automatically then sooner or later you'll forget to run it manually, and at some point ship a broken app to your users. Running tests in your CI build also enables you to automate continuous deployment, which is always a giggle.