WinRunner

from Wikipedia, the free encyclopedia

WinRunner is part of the " Functional test software " components, the other part of which is QuickTestProfessional , an automatic GUI test tool that allows the user to record and replay interactions with the user interface of a software to be tested as test scripts . The tool uses a programmable test script language ( TSL ), which enables the changes and parameterization of the recordings, e.g. B. Black box test . It is manufactured by Mercury Interactive, which was acquired by Hewlett-Packard in 2006 . It is HP.com BTO software.

On February 15, 2008, HP announced the end of support for the following versions: 7.5, 7.6, 8.0, 8.2, 9.2 all versions, all editions. For details (by when, limitation, follow-up product / migration support) see the section on web links.

use

It is suitable for the automation of created regression tests in which test cases with data and navigation objects provide verifiable results for test coverage of software with GUI. The application is automated as black box tests on the graphical interface, true to the user . Programming is done in TSL. Test results are generated in order to obtain precise analyzes of the test cases. For this purpose, the return value is checked and added for verification after the action has been completed . Collected return values ​​must not be! = 0.

E.g .: 

public function FRM_Benutzer_Daten ( in table, in test, in idx, in mode )
{
 auto rc;
 rc = FRM_init_block( table, test, idx, mode );
 if ( rc != E_OK )
  return rc;
 rc+=FRM_set_window ("Administration_Benutzer_Bearbeiten", 5);
 rc+=FRM_edit_set ( table, test, "Benutzername" );
 rc+=FRM_edit_set ( table, test, "Vollständiger Name" );
 rc+=FRM_edit_set ( table, test, "Passwort" );
 rc+=FRM_edit_set ( table, test, "Paßwortbestätigung" );
 rc+=button_press( "OK" );
 return rc;
}

Ideally, the result is automatically linked to the requirements , which only enables a real analysis of the test coverage. That means about all objects, interfaces, equivalence class tests , subject tests and interdisciplinary requirements. This is set in the HP QualityCenter, a web-based system for automated quality tests and the management of software.

Recording variants

There are two ways to record a test with WinRunner:

  • Analog recording : All mouse movements, clicks and keystrokes are recorded and can be played back later. However, this method is relatively critical, since objects can change their place with newer program versions.
  • Context-sensitive recording : The objects of the graphical user interface are addressed directly, so that e.g. For example, a “Next” button is pressed even if the developers have moved it to a different position in a newer version.

Extensions

There are several add-ins for the software:

Custom C / S

  • Windows
  • C ++ / C
  • Visual Basic
  • PowerBuilder
  • Forte
  • Delphi
  • Centura
  • Stingray
  • Small talk

ERP / CRM

  • Baan
  • PeopleSoft Windows
  • SAP ERP 6.0 with a special patch
  • Siebel 5, 6 GUI clients
  • Oracle GUI Forms
  • Oracle: Jinitiator, 11i, NCA
  • JD Edwards Web Client

Web-Related Environments

  • IE, Netscape, AOL
  • JDK, Java Foundation Classes, AWT
  • Symantec Visual Café
  • ActiveX controls

As well as interfaces to other test tools such as LoadRunner, Stingray, Topaz, which are also sold by HP BTO (formerly Mercury Interactive), but also open source projects such as the EMOS framework for keyword-driven testing .

Versions (since 2001)

  • Version 7.0 was released in March 2001
  • Version 7.6 was released in January 2004
  • Version 8.0 (not very stable) was released in January 2005
  • Version 8.2 was released on August 18, 2005
  • Version 9.2 (current) was released in March 2007

distribution

WinRunner is not very common in the German-speaking world, it is mainly used in England , the USA and India .

See also

Manuals

Open source frameworks for WinRunner

Web links