1 / 33

Automating your Website Testing

Automating your Website Testing. By Andrew L. Pollner and Lei Wang ALP International Corporation. Why Load Test?. To Simulate Multiple Users on a System To Measure end-to-end performance To Measure Server Performance: Database (Oracle) Application (CF) Middleware (Web Logic)

cheryl
Télécharger la présentation

Automating your Website Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Automating your Website Testing By Andrew L. Pollner and Lei Wang ALP International Corporation

  2. Why Load Test? • To Simulate Multiple Users on a System • To Measure end-to-end performance • To Measure Server Performance: • Database (Oracle) • Application (CF) • Middleware (Web Logic) • Web (Netscape)

  3. When Should Loadtesting Occur? • When sizing a server • After Application Has Stabilized • When other users are not on the system • After notifying Sys Admin.s, DBA’s, Test Managers

  4. What’s Needed for Loadtesting? Knowledge of: • Application • Database • Environment • LoadRunner!

  5. Transaction Rendezvous Measured event (i.e. Time it takes to return data to a screen after a QUERY button is pressed) Synchronized point where transaction is to occur simultaneously Loadtesting Concepts - Part I

  6. Vuser Sgroup Scenario A defined user type which executes a specific test A group of Vusers which with a characteristic profile A combination of sgroups Loadtesting Concepts - Part II

  7. Types of Vusers • Web • C/S GUI • Terminal Emulation • SQL

  8. Using LoadRunner - Web • Record HTTP Script • Generalize trace • Add Transaction points: • start_transaction(“ClaimWriteback”) • end_transaction(“ClaimWriteback”, PASS) • Add Rendezvous: • rendezvous(“Login”) rendezvous(“ClaimWriteback”)

  9. Login Login Login Enter Data Enter Data Enter Data Save Data Save Data Save Data Start Synchronization Rendevouz 1 ==> Rendevouz 2 ==> Rendevouz 3 ==>

  10. Login Enter Data Login Save Data Enter Data Login Save Data Enter Data Save Data Step Synchronization Rendevouz 1 ==> Rendevouz 2 ==> Rendevouz 3 ==>

  11. Using LoadRunner - DB • Get SQL trace • Generalize SQL trace • Add Transaction points: • start_transaction(“ClaimWriteback”) • end_transaction(“ClaimWriteback”, PASS) • Add Rendezvous: • rendezvous(“Login”) rendezvous(“ClaimWriteback”)

  12. Product Categories • GUI/Web vusers • Netscape Browser • IE Browser • Client Server • RTE vusers • Terminal Emulation • SQL (dB) vusers • Client Server

  13. LoadRunner Family of Products • Both Client AND Server Load Testing • Wide range of platforms • Win 2000 • NT • Win95/98 • UNIX • Reporting • Automatically for each user • By transaction

  14. WAN/ Internet Client AND Server Load TestingTesting the Site • Single point of control: Controller SYBASE SERVER SQL SERVER NT

  15. WAN/ Internet Client AND Server Load TestingTesting the Site • Single point of control: Controller • Drive multiple real NT GUI clients :End-to-End SYBASE SERVER SQL SERVER NT

  16. WAN/ Internet Client AND Server Load TestingTesting the Site • Single point of control: Controller • Drive multiple real NT GUI clients : End-to-End • Stress SQL Server with multiple virtual NT clients SYBASE SERVER NT SQL SERVER NT

  17. WAN/ Internet Client AND Server Load TestingTesting the Enterprise • Single point of control • Drive multiple real clients • Stress SQL Server virtual clients NT • Stress Sybase: virtual clients NT/UNIX SYBASE SERVER NT NT/UNIX

  18. Advanced Loadtest Measurement • Mean vs. Median • 90% Percentile • Performance under load • System Performance Measurement • CPU • SWAP • DISK

  19. GUI Application Protocol Analyzing Loadtest Results - I CLIENT LAN SERVER WAN SERVER Sybase SQL Server Total System Performance: Client, LAN, SQL Server, WAN, Sybase Client Load

  20. GUI Application Protocol Analyzing Loadtest Results - II CLIENT LAN SERVER WAN SERVER Sybase SQL Server Client Load Transaction Performance: LAN, SQL Server, WAN & Sybase Server Load

  21. GUI Application Protocol Analyzing Loadtest Results - III CLIENT LAN SERVER WAN SERVER Sybase SQL Server Client Load Transaction Performance: WAN, Sybase Server Load

  22. GUI Application Protocol Analyzing Loadtest Results - IV CLIENT LAN SERVER WAN SERVER Sybase SQL Server Client Load Server Load Transaction Performance: SYBASE

  23. GUI Application Protocol Analyzing Loadtest Results - V CLIENT LAN SERVER WAN SERVER Sybase SQL Server Client Load Transaction Response Time: Client Transaction Response Time: LAN, SQL Server Server Load

  24. Conclusions Loadtesting: • Is a necessary component in testing an application and its environment • Has multiple purposes • Comes in many flavors • Is an extension to Functional testing • Is complex!

  25. DEMO!

  26. Virtual User Generator

  27. LoadRunner Controller

  28. Controller Vusers

  29. Vuser Protocol

  30. Transaction Report

  31. Page Faults Graph

  32. On-line Monitors

  33. Q&A

More Related