Use Intern for JavaScript unit testing

With so much of JavaScript in use on and off the web and a growing library where I work, there is a need for good unit testing.  I have spent time looking at many of the different tools, though they have not been quite adequate for all of our needs.  I have recently been pointed towards Intern, a new project by SitePen Labs.

Javascript libraries

There are many discussions (some quite heated) on what JavaScript library/framework is better.  I believe it all depends on your own abilities, needs, and intentions.  There are many developers working with all the popular libraries and frameworks.  Can all front-end developers be wrong?  In contrast I have seen many developers who have opted to not use a library and decide to do it all on their own.  This often strikes me as odd in some of these situations, since I usually don't care to reinvent if there is not a valid reason.  There are some elements of a framework I feel necessary when coding JavaScript for a large system in a fast paced work environment.  I am going to touch on a couple of these.

WebSphere Commerce Data Services Layer

In my last post, I introduced concepts and layers around the BOD framework.  Now I plan to dig a little more into the framework and discuss an important layer within the framework, DSL.

The WebSphere Commerce BOD framework often refers to the data services layer (DSL).  For those familiar with the NVP command programming model, the DSL replaces the EJBs and Access Beans.  It provides the abstract layer for data access decoupled from the physical database schema.  I am going to try to pull some of the information together for a decent overview of DSL.

Here is a high level view from the info center of where in the architecture the DSL fits in.

BOD, What is it? Should I use it?

WebSphere Commerce BOD, this architecture in WCS is not as straight forward to follow at first, unlike the NVP Command framework.  As WebSphere Commerce is transitioning to SOA, there is a need to ensure decoupling of the various components and allow re-use of the WebSphere Commerce business services. The result is a change to the frameworks driving development within WCS.  This is where the BOD framework comes in.

So what is BOD?

WCS Development Framework ...

For a long time working with WCS storefronts meant learning and developing on top of a single framework, name-value pair controller and task commands. Later there were access beans and EJB's added to that line up. Now though looking into WCS you see what seems confusion of identity around the framework. This is because of the BOD and SDO and DSL framework.

Since IBM is always building and following new technology fads, their system has taken on multiple framework identities.

Articles coming soon ...

example:

BOD Command/SDO vs NVP Command/Access Bean/EJB