Jim Holmes
Jim is an Executive Consultant at Pillar Technology. He is also the owner of Guidepost Systems. He has been in various corners of the IT world since joining the US Air Force in 1982. He’s spent time in LAN/WAN and server management roles in addition to many years helping teams and customers deliver great systems. Jim has worked with organizations ranging from startups to Fortune 100 companies to improve their delivery processes and ship better value to their customers. When not at work you might find Jim in the kitchen with a glass of wine, playing Xbox, hiking with his family, or banished to the garage while trying to practice his guitar.
-
-
Cloud Mobile
Cloud for the Entire Lifecycle
Using Telerik Platform's cloud-based services enables you to avoid unnecessary development and infrastructure efforts, and instead focus on delivering great value to your customers.February 07, 2014
by Jim Holmes
-
.NET Kendo UI Mobile Web
Four UI Test Automation Tips for HTML5 Applications
Every application needs a solid mix of automated testing: unit, integration, and functional/User Interface. UI automation has always been at the top of the test pyramid, but not because they’re the best type of automated tests. Rather, UI tests should be a few carefully chosen tests built on top of a wide base of unit tests and a solid middle layer of integration tests.June 19, 2013
by Jim Holmes
-
.NET Kendo UI Mobile Web
HTML5 and Test Studio
Rich user experiences with HTML5 applications can cause some difficulties for teams trying to get solid user interface (UI) testing around their apps. Interacting with video or audio elements is often troublesome, and the manipulations of a web page’s document object model (DOM) on the fly via asynchronous alterations causes automation frameworks (and automaters!) endless grief in the attempt to get subtle timing issues stabilized.April 25, 2013
by Jim Holmes
-
.NET Mobile
Avoid Failing Tests When Automating Dynamic Ajax Requests
My advice: DO NOT EVER rely on execution delays, manual pauses, or Thread.Sleep() to handle your tests’ timing issues. Ever. Period. Instead, figure out exactly what condition you need to move forward with your test, then create an explicit wait for that condition. This is a rock-solid pattern that works in nearly every situation. Here’s a practical example for you using Telerik’s neat demo of our RadComboBox.April 22, 2013
by Jim Holmes