1. Test data(User Name, Password etc)
2. Type of testing:
* Load Testing
* Stress Testing
* Endurance Testing
3. Specific time that when the scripts can be executed.
4. Architecture of the application
5. Load Generator
6. Server configuration
7. Expected Delay Time.
8. Expected Throughput time.
9. Exact bandwidth.
10. How many users going to access the application?
11. How many concurrent users?
12. What are the roles of the users?
13. Type of the application.
14. What are all the protocols using?
15. How many peak users?
16. What type of scenarios facing?
17. How often the peaks and when they are occurring?
Showing posts with label loadrunner. Show all posts
Showing posts with label loadrunner. Show all posts
Saturday, January 31, 2009
Status in Loadrunner controller Scenario Groups

Scenario Groups pane in the Run view of controller is to monitor the actions of all the Vusers and Vuser groups in the scenario.
The Status field of each Vuser group displays the current state of each Vuser in the group
1. Down Status: Vuser is down
2. Pending: Vuser is ready to be initialized and waiting for an available load generator
3. Init: The Vuser is being initialized on the remote machine.
4. Ready : The Vuser already performed the init section of the script and is ready to run.
5. Running: The Vuser is running. The Vuser script is being executed on a load generator
6. Rendezvous: The Vuser has arrived at the rendezvous and is waiting to be released by LoadRunner.
7. Done.Passed : The Vuser has finished running. The script passed.
8. Done.Failed : The Vuser has finished running. The script failed.
9. Error: A problem occurred with the Vuser
10. Gradual Exiting : The Vuser is completing the iteration or action it is running Before exiting.
11. Exiting : The Vuser has finished running or has been stopped, and is now exiting.
12. Stopped The Vuser stopped when the Stop command was invoked.
Available Protocols in Loadrunner 8.0
1. Application Deployment Solution Protocol: Citrix protocol.
2. Client/Server Protocols : DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols.
3. Custom Protocols: C templates, Visual Basic templates, Java templates, Java script and VBscript type scripts
4. Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java
5. E-business protocols: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, Dual Web/Winsocket protocols.
6. Enterprise Java Beans Protocols: EJB Testing and Rmi-Java protocols.
7. ERP/CRM protocols: For Baan, Oracle NCA, People soft-Tuxedo, People soft 8,
8. SAPGUI, SAP protocols -Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols.
9. Legacy protocols: For Terminal Emulation (RTE).
10. Mailing Services protocols: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.
11. Middleware protocols: Jacada and Tuxedo (6, 7) protocols.
12. Streaming Protocols: For Media Player and RealPlayer protocols.
13. Wireless Protocols: For i-Mode, VoiceXML, and WAP protocols.
2. Client/Server Protocols : DB2 CLI, DNS, MS SQL, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols.
3. Custom Protocols: C templates, Visual Basic templates, Java templates, Java script and VBscript type scripts
4. Distributed Components: For COM/DCOM, Corba-Java, and Rmi -Java
5. E-business protocols: For FTP, LDAP, Palm, Web (HTTP/HTML), Web Services, Dual Web/Winsocket protocols.
6. Enterprise Java Beans Protocols: EJB Testing and Rmi-Java protocols.
7. ERP/CRM protocols: For Baan, Oracle NCA, People soft-Tuxedo, People soft 8,
8. SAPGUI, SAP protocols -Web, and Siebel (Siebel-DB2CLI, Siebel-MSSQL, Siebel-Web, and Siebel-Oracle) protocols.
9. Legacy protocols: For Terminal Emulation (RTE).
10. Mailing Services protocols: Internet Messaging (IMAP), MS Exchange (MAPI),
POP3, and SMTP.
11. Middleware protocols: Jacada and Tuxedo (6, 7) protocols.
12. Streaming Protocols: For Media Player and RealPlayer protocols.
13. Wireless Protocols: For i-Mode, VoiceXML, and WAP protocols.
Subscribe to:
Posts (Atom)