English | German | French | Portugese | Italian |
Wednesday, May 18, 2022
Software Testing
  • Introdução
  • Processo testando do começo
  • Processo testando do batente
  • Estratégia testando
  • Planta testando
  • Análise do risco
  • Ciclo de vida testando do software
    Software Testing Types
  • Testar de estática
  • Testar dinâmico
  • Testar de Blackbox
  • Testar de Whitebox.
  • Testar da unidade.
  • Testar das exigências.
  • Testar da regressão.
  • Manipulação de erro testando.
  • Testar da sustentação manual.
  • Testar Intersystem.
  • Controlar testar.
  • Paralelizar testar.
  • Testar do volume.
  • Testar do Stress.
  • Testar de desempenho.

    Testing Tools
  • Corredor da vitória
  • Corredor da carga
  • Testar o diretor
  • Teste de seda
  • Testar o sócio

    Interview Question
  • Ganhar o corredor
  • Carregar o corredor
  • Teste de seda
  • Testar o diretor
  • Pergunta testando geral


    Pergunta da entrevista de LoadRunner

    A D V E R T I S E M E N T

    1. Explain the recording mode for web Vuser script? - We use VuGen to develop a Vuser script by recording a user performing typical business processes on a client application. VuGen creates the script by recording the activity between the client and the server. For example, in web based applications, VuGen monitors the client end of the database and traces all the requests sent to, and received from, the database server. We use VuGen to: Monitor the communication between the application and the server; Generate the required function calls; and Insert the generated function calls into a Vuser script.
    2. Why do you create parameters? - Parameters are like script variables. They are used to vary input to the server and to emulate real users. Different sets of data are sent to the server each time the script is run. Better simulate the usage model for more accurate testing from the Controller; one script can emulate many different users on the system.
    3. What is correlation? Explain the difference between automatic correlation and manual correlation? - Correlation is used to obtain data which are unique for each run of the script and which are generated by nested queries. Correlation provides the value to avoid errors arising out of duplicate values and also optimizing the code (to avoid nested queries). Automatic correlation is where we set some rules for correlation. It can be application server specific. Here values are replaced by data which are created by these rules. In manual correlation, the value we want to correlate is scanned and create correlation is used to correlate.
    4. How do you find out where correlation is required? Give few examples from your projects? - Two ways: First we can scan for correlations, and see the list of values which can be correlated. From this we can pick a value to be correlated. Secondly, we can record two scripts and compare them. We can look up the difference file to see for the values which needed to be correlated.  In my project, there was a unique id developed for each customer, it was nothing but Insurance Number, it was generated automatically and it was sequential and this value was unique. I had to correlate this value, in order to avoid errors while running my script. I did using scan for correlation.
    5. Where do you set automatic correlation options? - Automatic correlation from web point of view can be set in recording options and correlation tab. Here we can enable correlation for the entire script and choose either issue online messages or offline actions, where we can define rules for that correlation. Automatic correlation for database can be done using show output window and scan for correlation and picking the correlate query tab and choose which query value we want to correlate. If we know the specific value to be correlated, we just do create correlation for the value and specify how the value to be created.
    6. What is a function to capture dynamic values in the web Vuser script? - Web_reg_save_param function saves dynamic data information to a parameter.
    7. When do you disable log in Virtual User Generator, When do you choose standard and extended logs? - Once we debug our script and verify that it is functional, we can enable logging for errors only. When we add a script to a scenario, logging is automatically disabled. Standard Log Option: When you select
      Standard log, it creates a standard log of functions and messages sent during script execution to use for debugging. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled Extended Log Option: Select
      extended log to create an extended log, including warnings and other messages. Disable this option for large load testing scenarios. When you copy a script to a scenario, logging is automatically disabled. We can specify which additional information should be added to the extended log using the Extended log options.
    8. How do you debug a LoadRunner script? - VuGen contains two options to help debug Vuser scripts-the Run Step by Step command and breakpoints. The Debug settings in the Options dialog box allow us to determine the extent of the trace to be performed during scenario execution. The debug information is written to the Output window. We can manually set the message class within your script using the lr_set_debug_message function. This is useful if we want to receive debug information about a small section of the script only.
    9. How do you write user defined functions in LR? Give me few functions you wrote in your previous project? - Before we create the User Defined functions we need to create the external
      library (DLL) with the function. We add this library to VuGen bin directory. Once the library is added then we assign user defined function as a parameter. The function should have the following format: __declspec (dllexport) char* <function name>(char*, char*)Examples of user defined functions are as follows:GetVersion, GetCurrentTime, GetPltform are some of the user defined functions used in my earlier project.
    10. What are the changes you can make in run-time settings? - The Run Time Settings that we make are: a) Pacing - It has iteration count. b) Log - Under this we have Disable Logging Standard Log and c) Extended Think Time - In think time we have two options like Ignore think time and Replay think time. d) General - Under general tab we can set the vusers as process or as multithreading and whether each step as a transaction.
    A D V E R T I S E M E N T




    A D V E R T I S E M E N T

    Rede de Vyom: SMS livre, GRE, GMAT, MBA | Exams em linha | trabalhos de Freshers | Downloads do software | códigos da programação & de fonte | Deli Info | trabalhos, discussões | papéis da colocação | eBooks livres | eBooks livres | negócio livre Info | perguntas da entrevista | Tutorials livres | árabe, francês, alemão | preparação de IAS | gracejos, canções, divertimento | Classifieds livre | receitas livres | Downloads livres | Bangalore Info | soluções do Tech | Outsourcing do projeto, hospedar da correia fotorreceptora | preparação da PORTA | preparação do MBA | SAP Info | testar do software

    Copyright © 2006. Cool Interview .com. All rights reserved
    The site is maintained by Vyom Technosoft Pvt. Ltd.