LOGIN | REGISTER NOW | SUBSCRIBE
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 7/1/2009 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
Is the mystery Borland suitor Serena?
Borland software is considering an offer from another company after a preliminary deal with MicroFocus. Is Serena the new company?
06/30/2009 01:55 PM EST

Windows 7 - An eBayer's dream product?
Windows 7 pre-orders can make people money on eBay.
06/29/2009 03:48 PM EST

Know thine cloud provider
Cloud computing require companies to understand compliance and regulation. Third parties will play a big role in regulated industries.
06/29/2009 02:58 PM EST

 

Microsoft Worldwide Partner Conf.
7/13/2009 to 7/16/2009
New Orleans
Microsoft

OSCON (Open Source Convention)
7/20/2009 to 7/24/2009
San Jose
O'Reilly Media

XBRL Technology Workshop & Summit
7/28/2009 to 7/30/2009
Santa Clara
XBRL US

ACM SIGGRAPH
8/3/2009 to 8/7/2009
New Orleans
ACM SIGGRAPH

OpenSource World (formerly LinuxWorld)
8/12/2009 to 8/13/2009
San Francisco
IDG World Expo


 
print Printable version 
Most Read Latest News Blog Resources
Kapow automates website data retrieval
Kapow Technology's Web Data Server 7.0 can be used to create modules that navigate through...

COBOL’s future lies in the clouds
After 50 years of use in businesses, COBOL is still lingering around mainframes. But the s...

Oracle's Fusion 11g lays groundwork for ERP platform
Fusion's components are standards-based and integrated, but some abilities are lost if non...

Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter

Lisa Dresses Up for Continuous Testing


iTKO tool upgrade now features dashboard for metrics, configurable notification

By David Rubinstein
October 1, 2006 — 
In a services world, organizations build their applications using externally created and managed components that change without their notice or approval, or that stop being upgraded, or that have unseen dependencies that can break an application.

Or, even within one company, there could be a mandate that it no longer is acceptable for each unit to maintain software similar to that being used and maintained in a different unit. Suddenly, one group is forced to face the problem of depending on software that other people manage and control.

So, an organization might deploy its application only once per year, but a Web services component of that app might be updated six times during the year. This creates testing issues for the organization releasing the application.

Into this scenario comes iTKO, which is defining a practice it calls continuous testing. “Testing is no longer an event along a static life cycle,” said iTKO founder and chief architect John Michelsen.

Michelsen said the “five nines” of application availability is actually a product of system uptime, application availability and—from a business perspective—functional integrity. The first two, he noted, can pretty much be automated to ensure uptime. The last one, though, is as critical to business as the first two. “Apps had better deliver the business functionality, or it’s downtime,” Michelsen said.

iTKO is expected on Oct. 2 to release version 3.5 of its Lisa automated testing platform, with more emphasis on managing continuous testing. New dashboard functionality has been built in so users can schedule tests, set, record and analyze pass/fail metrics and get other application data in a customizable format that makes the data most useful.

NOTICE OF FAILURE
Lisa 3.5 also now provides configurable “on failure” notification. “In a continuous [testing] service, various people need to be notified,” Michelsen explained. A functional test, for example, might fail, in which case both the developer and the business analyst who wrote the requirement would be notified.

A key to this kind of testing is to do the tests on the entire deployed application, Michelsen noted. “Usually you just test your piece of the app, not the whole millions-of-lines-of-code app,” he said. But with applications built from services, which are changing all the time, the application has to be checked at runtime to ensure business

continuity and functional integrity, he maintained. “Now,” Michelsen said, “it’s important to associate between the [application] staging and runtime areas. You must ensure functional integrity at runtime.”


Share this link: http://www.sdtimes.com/link/29637
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading