Server virtualization provides an immediate reduction in hardware and
configuration cost. But in focusing merely on the hardware side of
virtualization, are we leaving money on the table?
While organizations can reduce the number of boxes they need, and save the
cost of replicating servers for virtual test beds, these servers are becoming
commodities. What if we could apply the benefits of virtualization where we
spend 80 percent or more of the IT budget – in the key enterprise
software that runs our business and in the extensive development, support and
maintenance costs of these applications?
Today’s leading businesses rely on a mix of distributed technologies
and new functionality, such as service-oriented architecture (SOA).
Virtualization can improve the... (more)
Gone are the days when you could test an interface to a single client/server
app and know that you have performance covered. Today's interconnected
systems such as fully integrated packaged applications, ESB-based enterprise
platforms, and SOA make ensuring high-performance from application components
and solutions increasingly difficult. On top of that complexity, we are
increasingly su... (more)
Server virtualization provides an immediate reduction in hardware and
configuration cost. But in focusing merely on the hardware side of
virtualization, are we leaving money on the table?
While organizations can reduce the number of boxes they need, and save the
cost of replicating servers for virtual test beds, these servers are becoming
commodities.
What if we could apply the benefits ... (more)
John Michelsen's iTKO Blog
In this series we are going to look at four aspects of the Agile lifecycle:
test & quality management, application lifecycle management, IT operations,
monitoring and performance, IT and SOA governance.
For years, testing was an siloed activity that used different and unconnected
tools within specific phases of the application lifecycle. First, a
development team... (more)
John Michelsen's iTKO Blog
In the past, test “scripts” in TM tools were largely recorded as actual
step-by-step instructions (in a Word doc or Excel spreadsheet) for a manual
tester to point-and-click through a finished interface to test the
application. When tests were completed, the tester would then “check a
box” in the test management UI, to indicate that the test had passed or
fail... (more)