Recently We get a chance to taste the two flavors in performance automation tools as you all know, None other than the two world wide competitors Load runner(HP) and Silk Performer(Borland) :-)
Here we identified few features that are identical and unique in both tools. First let me list out Unique features in SilkPerformer and Loadrunner
Unique features for Silk Performer:
A load test is begun by creating a project that automatically keeps all information belonging to that project in a single project directory. So locating items associated with a certain project (e.g., scripts and test results) is easy and efficient.
-It is handling the load test in a sequence manner.
-It allows various profiles for different set of settings in project.
-We can set timers under transactions.
-We have to use try script (Reply) to make error free confirmation to proceed further.
-True log explorer is kind of visual scripting; through this we can customize correlation, parameterization, and content verification.
-It would not allow us into load test without finding the base line.
-With in a project, for every load test a result directory for each run is created.
-We can create our own behavior of end users.
-Root cause diagnostics, and code performance monitoring.
-We can generate the script in the middle of recording.
- Optical Character Recognition capabilities.
SP provide Optical Character Recognition (OCR) capabilities for text displayed in the Citrix client GUI.
Unique features for LoadRunner:
Two options for Error Logs:
Standard: When you selectStandard 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.
Extended: Enable this to including warnings and other messages. Disable this option for large load testing scenarios
Two options for Debug Vuser Script i) Run step by step command ii) Break prints.
Identical Features for Silk Performer:
Silk Performer components:
o Work bench
o Silk True log
o Silk Performance Explorer
Load Testing Process:
-configuring projects
-modeling projects
-validating projects
-customizing projects
-establishing base line performance
-define work load
-executing load test
-explore test results
Scripting language is BDL (Business Definition Language).
SP provides serialization or synchronization (Serialization enables you to test the effects of transactions executed one at a time).
Parameterization in Silk Performer.
-Go to customize test
-Create New Parameter wizard by selecting any one of them.
-Constant value.
-Parameter from Random variable.
-Parameter from multi column data file.
-Stress think time is nothing but ignore think time.
-We can use silk test script in Silk performer
Identical Features for Load Runner:
Load Runner components:
o The Vuser Generator
o The Controller
o Analysis
-Load Testing Process:
-Plan Load test
-Create Vuser Scripts
-Define Scenario
-Run a ScenarioAnalyze the Results
Scripting Language is in C or Visual Basic.
LR provides Rendezvous point (Rendezvous enables you to test the effects of transactions executed one at a time).
Parameterization in Load Runner.
Select the string which needs to be parameterized.
Mouse right clicks on string and replace with parameter.Select type of parameter.
Ignore think time is nothing but stress think time in SP.
Friday, January 4, 2008
Subscribe to:
Post Comments (Atom)
1 comment:
Thanks for this excellent write-up of your findings. I'm asked for comparisons of our PushToTest TestMaker tool to Silk and LoadRunner and your blog entry helps me. If you ever want a demo of PushToTest then just let me know (fcohen@pushtotest.com).
Thanks.
-Frank
Post a Comment