Open UI: Testing with Selenium

Thursday, October 23, 2014 | | 7 comments
Selenium is a browser automation tool, that allows web projects to automate repetitive tasks. As an early pioneer of Open UI, I found this new capability to be incredibly useful for achieving continuous integration. I gave readers a hint of this last year, in the article "Open UI - Build Process",...

Open UI: Grunt and JSHint

Thursday, September 18, 2014 | | 1 comment
Previously we looked at how Grunt can improve your Open UI development experience, by automatically reloading the browser, every time a source file is changed. This time we take another step, and configure an automated code check using Grunt and JSHint. Think of how Siebel Tools prevents you from compiling,...

Open UI: Grunt with Livereload

Wednesday, September 17, 2014 | | 2 comments
With Siebel Open UI development we naturally spend the majority of our time working on the browser. Part of that requires clearing the browser cache, and hitting F5 to reload the browser. Sometimes we reload the browser, and think afterwards, did I really clear the cache that time? Maybe not... so...

Siebel cScript

Wednesday, July 23, 2014 | | 2 comments
Introduction eScript is Siebel’s de-facto scripting language, but in an alternate universe, Siebel could have called its scripting language cScript, in reference to its C heritage. eScript is based on the ECMA Script standard (from which JavaScript is also based upon), and shares the same C family...

Anonymous functions in Siebel

Thursday, June 12, 2014 | | 8 comments
I was on a Project, that was performing an upgrade from Siebel 7 to Siebel 8, and discovered  parts of their Application was implemented using undocumented eScript features. The code was written by graduate web developers, who used their trade to write ECMA compliant code, but unfortunately some...

The Test

Friday, June 06, 2014 | | No comments
Every once in a while, a developer decides to make a fix without unit testing and breaks the application. There are a variety of reasons why it occurs, it could be that the developer got too confident, maybe it hard to setup the test case, it could be due to inexperience, or it could be due to pressure...
Subscribe to: Posts (Atom)