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


   

 
 
Download Current Issue
ISSUE 3/15/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
ASP.NET MVC 2 Ships
ASP.NET MVC 2 has shipped.
03/12/2010 10:26 AM EST

Microsoft plans 'open' Silverlight analytics framework
Microsoft is going to announce a multipurpose analytics framework for Silverlight at MIX.
03/11/2010 09:51 AM EST

About CSS processing
Two sites that lead to a startling CSS conclusion.
03/10/2010 02:29 AM EST

 

Events calendar tab
SHARE
3/14/2010 to 3/18/2010
Seattle, Wa.
SHARE

Cloud Connect
3/15/2010 to 3/18/2010
Santa Clara, Calif.
TechWeb

Microsoft MIX10
3/15/2010 to 3/17/2010
Las Vegas
Microsoft

SharePointPro Summit & Expo
3/16/2010 to 3/19/2010
Las Vegas
Penton Media

TheServerSide Java Symposium
3/17/2010 to 3/19/2010
Las Vegas
TechTarget


 
print Printable version 
Most Read Latest News Blog Resources
Even with its success, .NET causes some consternation
Despite its popularity, the developer community believes that .NET isn't being fully serve...

VMware releases Tomcat-based server for Spring
SpringSource and VMware are moving their platforms closer together with tc Server for Spri...

Appcelerator dev environment targets Android, iPhone
This unified development environment compiles JavaScript into Objective-C or Java, and wil...

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