As WinRunner runs tests, it simulates a human user by moving the mouse cursor over the application, clicking Graphical User Interface (GUI) objects, and entering keyboard input—but WinRunner does this faster than any human user. WinRunner is: Functional Regression Testing Tool Windows Platform Dependent. WinRunner is one of the popular tool used in software testing. Here is a list of commonly asked Interview Questions about WinRunner. Here is a list of commonly asked Interview Questions about WinRunner. HP WinRunner software was an automated functional GUI testing tool that allowed a user to record and play back user interface (UI) interactions as test scripts. Introduction First of all, I would like to give the brief description about WinRunner. It is a powerful automated testing tool developed by Mercury Interactive Company since it is basically used for functional regression testing. Also, It automates the testing process. Hence, to ensure that the applications performing as we expected or Not. It records operations as you perform them manually in your applications build and generates a test with required observation as checkpoints. In addition, you can run your test on application build and analyze the result manually with respect to the corresponding manual test case. Winrunner Testing Tool PdfThen, WinRunner enables you to adapt and reuse your tests for regression and protecting your effort in test creation. We are going to discuss various techniques and modes to record (like context sensitive and analog) a test case using win runner. So, we will understand how one can use WinRunner effectively to make the testing job easy. The salient that makes it different from other tools are • WinRunner is a functional testing tool. • As a result, it supports various technologies like VB, JAVA, Power Builder, DotNet, VC++, HTML, Delphi, Activex and ERP/Siebel technologies for automated functional testing. • It runs on a windows family operating systems only. • WinRunner converts our manual function tests into test script language (TSL) programs. To open WinRunner tool on the desktop, proceed this way: First of all, you need to follow these steps as follows, • Start->Programs->WinRunner->WinRunner TESTING PROCESS Testing with WinRunner includes four main stages- • Selecting manual functional test cases to be automated: First of all the automation test process starts with the selection of manual test cases to be automated by a testing Engineer. • Creating automated test scripts in TSL: After completing the first stage then, create the test using both recording and programming. Therefore recording tests, insert checkpoints where you want to check the behavior of the application under test(AUT). • Running Automated test scripts on the build: While running test cases, WinRunner emulates a user by entering mouse and keyboard input into your application. So, Each time the WinRunner encounters a checkpoint in the test, it compares the current response of your application to its expected response. • Analyzing automated test scripts results: When a test run ends, Furthermore, the test engineer can examine the result. While WinRunner lists all the major events that occurred during the run such as checkpoints. Manual Test case • Test case ID: Tc_xxx • Test case name: Verify OK button • Precondition: user ID and Password fields should take values. Test procedure: Step No Action Input Required Expected 1. Focus to Login OK button disabled 2. Enter user ID Valid value OK button disabled 3. Enter Password Valid value OK button disabled Entering username and password as action Test Script #Login set_window ('login', 8); button_check_info('OK','enabled',0); #check point edit_set('userid','asdf'); button_check_info('OK','enabled',0); #check point password_edit_set('password','yusufmalik@785'); button_check_info('OK','enabled',1); #check point button_press('ok'); Test script definition Finally, every automated test script program consists of navigational statements to operate build and checkpoints. To conduct required functional observation with respect to the corresponding manual functional test case. So, the scripting language tests script language for automating a manual test case. Because it is mercury interactive C-like Test scripting language. Therefore you create a test script by recording or programming TSL statements. Add-in Manager First of all, you need an Add-in manager window, as shown in the figure. After that, list out all WinRunner supported technologies with respect to purchased Add-in licenses. So, this window will open while launching WinRunner on our desktop. The Add-In Manager Dialog WinRunner also allows you to create automation test on selected technologies, which are used to implement your software build, in Add-in Manager. In above picture, a test engineer already selected ActiveX controls, PowerBuilder, and VisualBasic options. For this reason, WinRunner supports tests creation on your software build which is developed using selected technologies. Selain menggunakan tabel kebenaran, keekivalenan dapat dibuktikan dengan menggunakan dengan hukum-hukum logika, khususnya pada proposisi majemuk yang mempunyai banyak proposisi atomik. Contoh soal operasi himpunan matematika diskrit. Beberapa hukum tersebut mirip dengan hukum aljabar pada sistem bilangan riil, misalnya a(b+c) = ab + bc, yaitu hukum distributif,sehingga kadang-kadang hukum logika proposisi dinamakan juga hukum-hukum aljabar proposisi. HUKUM-HUKUM LOGIKA PROPOSISI Proposisi dalam hubungan ekivalensi logika, memenuhi sifat-sifat yang dinyatakan dalam sejumlah hukum. Berikut adalah simbol-simbol yang digunakan dalam logika predikat: • Simbol konstanta: a, b, c, d • Simbol variabel: x, y, z, w • Simbol fungsi: f, g, h • Simbol predikat: P, Q, R, S 4. Sebuah predikat seringkali menyatakan tentang sebuah hubungan relasional antara konstanta, variabel dan fungsi.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |