Thursday, 31 March 2016

What drawbacks do manual load tests have?

The manual load testing drawbacks are:
  • It is very expensive to do Manual Testing, as real users charge by the hour.
  • With manual load testing, load testing for longer durations like for 7 days won’t be possible, as users really work a maximum of eight hours daily.
  • You will not get accuracy for results correlation as there are delays between actions of users.
  • It is hard to do results collection as the results capture each other.
  • It is hard to do.

What are the criteria for entering and exiting in testing performance?

You can begin testing application performance during the designs. After evaluating these tests, you can collect and analyze the results for performance to be improved. The process of performance tuning will be done throughout the life cycle of the application development. Performance tuning is done based on factors like application release time and application stability user requirement, scalability under load, reliability, performance tolerance and stress tolerance criteria. The end criteria in some projects are defined based on the performance of the client, defined for each application section. When a product gets to the level expected then this is considered as performance testing end criteria.

Mention what is the benefit of LoadRunner on testing tools?

Benefit of LoadRunner testing tools is
  • Versatility
  • Test Results
  • Easy Integrations
  • Robust reports
  • Enterprise Package

Mention what are the phases for automated performance testing?

Phases for automated performance testing includes
  • Design or Planning
  • Build
  • Execution
  • Analyzing & Tuning

Explain what are the common mistakes done in Performance Testing?

The common mistakes done in Performance Testing are
  • Direct jump to multi-user tests
  • Test results not validated
  • Unknown workload details
  • Too small run durations
  • Lacking long duration sustainability test
  • Confusion on definition of concurrent users
  • Data not populated sufficiently
  • Significant difference between test and production environment
  • Network bandwidth not simulated
  • Underestimating performance testing schedules
  • Incorrect extrapolation of pilots
  • Inappropriate base-lining of configurations

How can you call a WinRunner script from LoadRunner?

 a.    First generate a scenario by exchanging the VUser script for a GUI WinRunner script.
b.    Select the Details option from the Host menu.
c.    Select the check box for GUI WinRunner.
d.    Finally, execute the scenario.

Can LoadRunner be used to test non-web based applications such as desktop applications?

 LoadRunner can be used for desktop applications. When the VU generator is started, it allows the tester to select the protocol that should be used. In addition to options for web-based applications, there are options for client/server applications as well.