It is official today 2/20/08 - below is from the HP announcement.
"IMPORTANT ANNOUNCEMENT FOR WINRUNNER USERS
HP Software is announcing end-of-support for HP WinRunner software, all versions (7.5, 7.6, 8.0, 8.2, 9.2). This end-of-support is based on our decision to consolidate and focus our functional testing offerings (HP WinRunner and HP QuickTest Professional) to maximize value to our customers."
I would humbly invite you to evaluate (or re-evaluate) SilkTest.
Rather than EOL SilkTest or offer a lightweight alternative and charge more, we are updating it with a new architecture, and, we offer a Borland service that can migrate your TSL scripts over to 4Test. I encourage everyone to take this very seriously, and in fact, PM me directly for details about our migration service.
The first victim - support.
The second victim - WinRunner - OMG! The world has ended. The sky is falling!
From the JP newswire:
Borland was scrambling today to quickly win over Winless WinRunner losers as HP announced plans to send WinRunner to the automation test tool graveyard. "High-fives" were abundant at Borland headquarters. A large force of marketing folks were called in to man the telephone banks and launch batches of Borland automated sales calls to HP customers. The phone call automation is ironically powered by HP's WinRunner. At HP headquarters, WTFs (WinRunner Task Forces) were assembled to handle customer WTF calls.
I just recently discovered AutoIT (freeware) and basically I can accomplish almost the same as with WinRunner. Less object recognition but the ones I need are in there. Luckily enough I only have to rewrite the framework (which interprets excel testscripts) of about 10.000 lines of TSL code.