Perceiver Monitoring tool
Perceiver is the new monitoring tool.This is introduced because Companies invest in enterprise applications and infrastructure to deliver optimal service to their end-user community. IT organizations are asked to manage more systems with fewer resources, while reducing costs. Performance Analysts and Capacity Planners are often asked to create volumes of custom charts and graphs for different audiences, instead of focusing on high value capacity planning and performance engineering responsibilities that provide a greater return on investment for the company.For this it is the best solution to use the BMC perceiver tool. KEY BENEFITS : User interface allows non-experts to easily access actionable data Ad hoc queries to track, view, and relate performance metrics to business applications Common interface for enterprisewide systems and applications Out-of-the-box value with BMC best practices view FEATURES : 1.Enhances decision-making capabilities by providing direct access to relevant performance data through a dynamic Web interface 2.Provides ad-hoc queries to track, view and relate detailed performance metrics to business applications 3.Increases the visibility and success of the performance organization by providing a consumer viewing tool for internal customers 4. Simplifies training and use via an easy-to-use web interface, eliminating the need for expert users and additional in-depth training 5. Maximizes the investment in BMC Performance Assurance by greatly increasing the number of direct users 6. Delivers out-of-the-box value with pre-loaded BMC Software Best Practice views including an online drag and drop editor for customization 7. Protects your performance investment by providing a performance viewing tool available across multiple platforms ABOUT BMC SOFTWARE BMC Software delivers the solutions: IT needs to increase business value through better management of technology and IT processes. Our industry-leading Business Service Management solutions help you reduce cost, lower risk of business disruption, and benefit from an IT infrastructure built to support business growth and flexibility. Only BMC provides best-practice IT processes, automated technology management, and award-winning BMC Atrium technologies that offer a shared view into how IT services support business priorities. Known for enterprise solutions that span mainframe, distributed systems, and enduser devices, BMC also delivers solutions that address the unique challenges of the midsized business. Founded in 1980, BMC has offices worldwide and fiscal 2008 revenues of $1.73 billion. Activate your business with the power of IT. www.bmc.com Source: http://discovery.bmc.com/
Posted by raviteja gorentla 2 comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Analysis, Controller, Errors in LoadRunner, ExtraStuff, General, LoadRunner, Manual Testing, Monitoring, Performance Testing,PerformanceCenter, Scripting, Tips n Tricks, Vugen
CPU of Load Generator Exceeded 80%
Recently i ran in to a load test and i saw the CPU of Load Generator Exceeded 80% and here are the ways to find out the root cause: There could be several things, but using 2008 machines on VMs is common. If you are using web vusers should be a small footprint.
Check if you have admin rights on the system or not?
Is CPU consumption above 80% during the entirety of the test
Check for any mismatch in versions in patch version
Try to run the agent using "Run as administrator"
Check for the mdrv process in the htask manager of the controller and the load generator machines while running the test
make sure to have the same patches level on every component, having a version mix is a real problem.
Please check if you have the following components installed on your LG machine McAfee Antivirus or Symantec NetBackup
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Analysis, Controller, LoadRunner, Performance Testing, PerformanceCenter, Scripting, Tips n Tricks, Vugen
"Error -27778: SSL protocol error when attempting to connect with host" in load runner
Recently i had some issues with SSL protocol error,while running the scripts in controller i am facing the "Error -27778: SSL protocol error when attempting to connect with host",so finally i got rid of that by using the below steps in the script Keep the below code at the start of of script use web_set_sockets_option("SSL_VERSION", "TLS"); web_set_sockets_option("SSL_VERSION", "1"); This forces the SSL connection to the server to use version 1 of the SSL protocol rather than letting the server suggest a version during the connection handshake. We had same issue on vugen 11.50 with new patch also then we enabled the below setting Run-Time Settings -> Preferences -> Select "WinInet Replay Engine instead of Sockets (Windows Only)."
Posted by raviteja gorentla 2 comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, General, Performance Testing, Scripting, Vugen
"HttpSendRequest" failed, Windows error code=12002 - Perf Center Error_load runner error
While running an internal application using the load runner Controller i was getting the "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error .I solved these by following the below steps:
1.Check Vugen runs script as a process or running vusers asa thread?
You can check this in Run time settings-General-Miscellaneous-Multithreading then uncheck the value 2.Are you working with WinInet, and the error itself comes from WinInet API not specifically Vugen.We can see in part of the replay errors comes from resources during the replay where they were timed out.
If we are forced to use WinInet then this will occur, but if you can use Sockets you may want to try that option instead or a Click and Script protocol.
you can uncheck the WinInet replay instead of sockets (Windows only) in the runtime settings-preferences.This will solve the problem.
3.And the another option is to use web_set_max_retries ("X") to increase the limit of 30 sec.You can place this before the action which is failing but I wouldn't recommend that. HttpSendRequest time out only occurres when any transaction takes more than 30 sec to connect to server. This default 30 sec time is because of the use of WinInet Replay engine. Thus this error pops up when you are running script with winInet replay and transactions are taking more than 30 sec. Only thing to get rid of this error is to fine tune the whole system and check the backend and servers to see any request que has formed up.
Posted by raviteja gorentla 3 comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Errors in LoadRunner, ExtraStuff, General, LoadRunner, Performance Testing, Scripting, Tips n Tricks, Vugen
HTTP WATCH
Why do you need an HTTP Viewer or Sniffer? All web applications make extensive use of the HTTP protocol (or HTTPS for secure sites). Even simple web pages require the use of multiple HTTP requests to download HTML, graphics and javascript. The ability to view the HTTP interaction between the browser and web site is crucial to these areas of web development:
Trouble shooting
Performance tuning
Verifying that a site is secure and does not expose sensitive information
How can HttpWatch Help?
HttpWatch integrates with Internet Explorer and Firefox browsers to show you exactly what HTTP traffic is triggered when you access a web page. If you access a site that uses secure HTTPS connections, HttpWatch automatically displays the decrypted form of the network traffic. Conventional network monitoring tools just display low level data captured from the network. In contrast, HttpWatch has been optimized for displaying HTTP traffic and allows you to quickly see the values of headers, cookies, query strings . HttpWatch also supports non-interactive examination of HTTP data. When log files are saved, a complete record of the HTTP traffic is saved in a compact file. You can even examine log files that your customers and suppliers have recorded using the free Basic Edition.
Why HttpWatch? Seven reasons to use HttpWatch rather than other HTTP monitoring tools:
Easy to Use - start logging after just a couple of mouse clicks in Internet Explorer or Firefox. No other proxies, debuggers or network sniffers have to be configured
Productive - quickly see cookies, headers, POST data and query strings without having to manually decode raw HTTP packets
Robust - reliably log thousands of HTTP transactions for hours or days while tracking down intermittent problems
Accurate - HttpWatch has minimal impact on the normal interaction of the browser with a web site. No extra network hops are added, allowing you to measure real world HTTP performance
Flexible - HttpWatch only requires client-side installation and will work with any server side technology that renders HTML pages in Internet Explorer or Firefox. No special server-side permissions or configurations are required - ideal for use against production servers on the Internet or Intranet
Comprehensive - works with HTTP compression, redirection, SSL encryption & NTLM authentication. A complete automation interface provides access to recorded data and allows HttpWatch to be controlled from most popular programming languages.
Professional Support - updates and bug fixes are provided free of charge on our website and technical support is available by email, phone or fax.
Uses of HttpWatch:
Testing a web application to ensure that it is correctly issuing or setting headers that control page expiration
Finding out how other sites work and how they implement certain features
Checking the information that the browser is supplying when you visit a site
Verifying that a secure web site is not issuing sensitive data in cookies or headers
Tuning the performance of a web site by measuring download times, caching or the number of network round trips
Learning about how HTTP works (useful for programming and web design classes)
Alowing webmasters to fine tune the caching of images and other content
Performing regression testing on production servers to verify performance and correct behavior
Posted by raviteja gorentla 1 comment:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, JMeter, Monitoring, Performance Testing, Scripting, Tips n Tricks, Vugen
What is a HAR File and what is the use of HAR??
HAR stands for HTTP Archive.
This is a common format for recording HTTP tracing information. This file contains a variety of information, but for our purposes, it has a record of each object being loaded by a browser. Each of these objects’ timings is recorded. The HAR file format is still an evolving standard, and the information contained within is both flexible and extensible. You should expect the HAR file to include a breakdown of timings including:
how long it takes to fetch the DNS information
how long each object takes to be requested
how long it takes to connect to the server
how long it takes to transfer from the server to the browser of each object
whether the object is blocked or not
The data is stored as a JSON document and extracting meaning from the low level data is not always easy, but with practice, a HAR file can quickly help you identify the key performance problems with a web page, which in turn will help you efficiently target your development towards the areas that will deliver the greatest return on your efforts.
Posted by raviteja gorentla 1 comment:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, General, LoadRunner, Performance Testing, Scripting, Tips n Tricks, Vugen
Base64 Encode/Decode for LoadRunner
Code:
#include "base64.h"
vuser_init()
{
int res;
// ENCODE
lr_save_string("ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789","plain");
b64_encode_string( lr_eval_string("{plain}"), "b64str" );
lr_output_message("Encoded: %s", lr_eval_string("{b64str}") );
// DECODE
b64_decode_string( lr_eval_string("{b64str}"), "plain2" );
lr_output_message("Decoded: %s", lr_eval_string("{plain2}") );
// Verify decoded matches original plain text
res = strcmp( lr_eval_string("{plain}"), lr_eval_string("{plain2}") );
if (res==0) lr_output_message("Decoded matches original plain text");
return 0;
}
base64.h include file
/*
Base 64 Encode and Decode functions for LoadRunner
==================================================
This include file provides functions to Encode and Decode
LoadRunner variables. It's based on source codes found on the
internet and has been modified to work in LoadRunner.
Created by Kim Sandell / Celarius - www.celarius.com
*/
// Encoding lookup table
char base64encode_lut[] = {
'A','B','C','D','E','F','G','H','I','J','K','L','M','N','O','P','Q',
'R','S','T','U','V','W','X','Y','Z','a','b','c','d','e','f','g','h',
'i','j','k','l','m','n','o','p','q','r','s','t','u','v','w','x','y',
'z','0','1','2','3','4','5','6','7','8','9','+','/','='};
// Decode lookup table
char base64decode_lut[] = {
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0,62, 0, 0, 0,63,52,53,54,55,56,57,58,59,60,61, 0, 0,
0, 0, 0, 0, 0, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,
15,16,17,18,19,20,21,22,23,24,25, 0, 0, 0, 0, 0, 0,26,27,28,
29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,
49,50,51, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, };
void base64encode(char *src, char *dest, int len)
// Encodes a buffer to base64
{
int i=0, slen=strlen(src);
for(i=0;i
{ // Enc next 4 characters
*(dest++)=base64encode_lut[(*src&0xFC)>>0x2];
*(dest++)=base64encode_lut[(*src&0x3)<<0x4 amp="" src="" xf0="">>0x4];
*(dest++)=((i+1)>0x6]:'=';
*(dest++)=((i+2)
}
*dest='\0'; // Append terminator
}
void base64decode(char *src, char *dest, int len)
// Encodes a buffer to base64
{
int i=0, slen=strlen(src);
for(i=0;i
{ // Store next 4 chars in vars for faster access
char c1=base64decode_lut[*src], c2=base64decode_lut[*(src+1)], c3=base64decode_lut[*(src+2)], c4=base64decode_lut[*(src+3)];
// Decode to 3 chars
*(dest++)=(c1&0x3F)<<0x2 amp="" c2="" x30="">>0x4;
*(dest++)=(c3!=64)?((c2&0xF)<<0x4 amp="" c3="" x3c="">>0x2):'\0';
*(dest++)=(c4!=64)?((c3&0x3)<<0x6 amp="" c4="" div="" x3f="">
}
*dest='\0'; // Append terminator
}
int b64_encode_string( char *source, char *lrvar )
// ----------------------------------------------------------------------------
// Encodes a string to base64 format
//
// Parameters:
// source Pointer to source string to encode
// lrvar LR variable where base64 encoded string is stored
//
// Example:
//
// b64_encode_string( "Encode Me!", "b64" )
// ----------------------------------------------------------------------------
{
int dest_size;
int res;
char *dest;
// Allocate dest buffer
dest_size = 1 + ((strlen(source)+2)/3*4);
dest = (char *)malloc(dest_size);
memset(dest,0,dest_size);
// Encode & Save
base64encode(source, dest, dest_size);
lr_save_string( dest, lrvar );
// Free dest buffer
res = strlen(dest);
free(dest);
// Return length of dest string
return res;
}
int b64_decode_string( char *source, char *lrvar )
// ----------------------------------------------------------------------------
// Decodes a base64 string to plaintext
//
// Parameters:
// source Pointer to source base64 encoded string
// lrvar LR variable where decoded string is stored
//
// Example:
//
// b64_decode_string( lr_eval_string("{b64}"), "Plain" )
// ----------------------------------------------------------------------------
{
int dest_size;
int res;
char *dest;
// Allocate dest buffer
dest_size = strlen(source);
dest = (char *)malloc(dest_size);
memset(dest,0,dest_size);
// Encode & Save
base64decode(source, dest, dest_size);
lr_save_string( dest, lrvar );
// Free dest buffer
res = strlen(dest);
free(dest);
// Return length of dest string
return res;
Posted by raviteja gorentla 1 comment:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, General, LoadRunner, Performance Testing, PerformanceCenter, Scripting, Tips n Tricks, Vugen
SCOM (System Center Operations Manager) Monitoring tool
System Center Operations Manager 2012 – the complete application monitoring solution For many years Operations Manager has delivered infrastructure monitoring, providing a strong foundation on which we can build to deliver application performance monitoring. It is important to understand that in order to provide the application level performance monitoring, we must first have a solid infrastructure monitoring solution in place. After all, if an application is having a performance issue, we must first establish if the issue is due to an underlying platform problem, or within the application itself. A key value that Operations Manager 2012 delivers is a solution that uses the same tools to monitor with visibility across infrastructure AND applications. To deliver application performance monitoring, we provide 4 key capabilities in Operations Manager 2012: Infrastructure monitoring – network, hardware and operating system Server-side application monitoring – monitoring the actual code that is executed and delivered by the application Client-side application monitoring – end-user experiences related to page load times, server and network latency, and client-side scripting exceptions Synthetic transaction – pre-recorded testing paths through the application that highlight availability, response times, and unexpected responses Configuring application performance monitoring So it must be hard to configure all this right? Lots of things to know, application domain knowledge, settings, configurations? Rest assured, this is not the case! We make it incredibly easy to enable application performance monitoring! 1. Define the application to monitor. 2. Configure server-side monitoring to be enabled and set your performance thresholds 3. Configure client-side monitoring to be enabled and set your performance thresholds And that’s it, you’re now set to go. Of course setting the threshold levels is the most important part of this, and that is the one thing we can’t do for you… you know your application and what the acceptable performance level is. Configuring an application performance dashboard in 4 steps It’s great that we make the configuration of application performance monitoring so easy, but making that information available in a concise, impactful manner is just as important. We have worked hard to make the creation of dashboards incredibly easy, with a wizard driven experience. You can create an application level dashboard in just 4 steps: 1. Choose where to store the dashboard 2. Choose your layout structure. There are many different layouts available. 3. Specify which information you want to be part of your dashboard. 4. Choose who has access to the dashboard. As you will see a little later in this article, publishing information through web and SharePoint portals is very easy. And just like that, you’ve created and published an application performance monitoring dashboard! Anyone who has either worked in IT, or been the owner of an application knows the conversations and finger pointing that can go on when users complain about poor performance. Is it the hardware, the platform, a code issue or a network problem? This is where the complete solution from Operations Manager 2012 really provides an incredible solution. It’s great that an application and associated resources are highly available, but availability does not equal performance. Indeed, an application can be highly available (the ‘5 nines’) but performing below required performance thresholds. The diagram below shows an application dashboard that I created using the 4 steps above for a sample application. You can see that the application is available and ‘green’ across the board. But the end users are having performance issues. This is highlighted by the client side alerts about performance. Deep Insight into application performance Once you know that there is an issue, Operations Manager 2012 provides the ability to drill into the alert down to the code level to see exactly what is going on and where the issue is. Reporting and trending analysis An important aspect of application performance monitoring is to be able to see how your applications are performing over time, and to be able to quickly gain visibility into common issues and problematic components of the application. In the report shown below, you can see that we can quickly see areas of the application we need to focus on, and also understand how these components are related to other parts of the application, and may be causing flow-on effects. Easily make information available With Operations Manager 2012, we have made it very easy to delegate and publish information across multiple content access solutions. Operations staff have access to the Operations Manager console, and we can now easily publish delegated information to the Silverlight based Operations web console and also to SharePoint webparts.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: LoadRunner, Monitoring, Performance Testing, PerformanceCenter, Scripting
How we will do Spike Testing and Explain it with example?
Spike Testing is a form of testing process in which an application is tested with unusual increment and decrements in the load. The system is unexpectedly loaded and unloaded. It is done to notice how actually the system reacts with unexpected rise and decline of users. Example:
when you are always checking the result of your exam on JNTU site means site is suddenly loaded and unloaded and then the IT squad of JNTU check how the site reacts with unexpected increase and decrease of users than it is Spike testing. Spike testing is mechanism of testing which means when in a web page frequent number of visitor access the page unexpectedly increases to maximum then obviously performance of the page breaks down. So the mechanism of testing a performance about web page due to unexpected sort of traffic on the page is always called as Spike testing. Spike testing is usually done by unexpectedly increasing the number of loads generated by users by a very enormous amount and observing the dramatic behavior of the system. The goal of spike testing is to regulate whether performance will deteriorate, the system will always fail, or it will be able to hold dramatic changes in load. A spike is a keen rise in the density for a given variable, generally immediately followed by a decrease. This category of transient variation is often notice in the measurement of voltage or you can say current in circuits. Spike testing is always used in load and performance testing. These tests are commonly based on real universe or projected workloads with focus on huge load/performance conditions.Spike testing is handling to check whether a system can handle dramatic changes in load. It is accomplish by spiking the no of users of an application and always produces an excellent way of verifying existing limitations in the current operational environment. spike testing is a type of performance testing.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: ExtraStuff, General, JMeter, LoadRunner, Performance Testing, PerformanceCenter, Scripting, Tips n Tricks
How does collating the test results work in loadrunner controller?
At the end of a test the results are collated by the LoadRunner controller. Each of the generators results are collected in a .eve (Event) file and the output messages for the controller are collected in a .mdb (Microsot Access) database. This happens in the directory specified for the results on the controller. A .lrr (loadrunner results) file is created. The .lrr file is text. The .eve file was text prior to around LoadRunner 7.5, but since then it has been an unpublished compressed format.
When you start the analysis utility it take the information in the .lrr file and the .eve file and creates a .mdb (microsoft access database) or SQL Server database entries which contain each timing record and data point entries. If collation fails at the end of the test you will have only partial results for analysis.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Analysis, Controller, General, LoadRunner, Performance Testing, Scripting
Error: "License cannot be save in your installation directory. (Error code = -4) It will be used only for this session."
Solution:
Make sure that you have administrator privilege to the Controller. If you are accessing the Controller via the network, make sure that you have write access to the network.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, LoadRunner, Manual Testing, Performance Testing, Scripting, Tips n Tricks,Vugen
Error “License security violation. Operation is not allowed”
Solution:
If you are applying “TEMPORARY” license, it will not work if LoadRunner was previously installed with a “TEMPORARY” or valid license key. You need to contact HP Customer Support for a valid license key.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, Performance Testing, Scripting
Error “License key was generated with a version superior to your license manager. Upgrade your license manager”
Solution:
Make sure the HostID that was sent to HP Customer Support was generated from the correct LoadRunner version. If you sent the HostID of LoadRunner 7.6, but apply the license key on LoadRunner7.0 install, you will get this problem.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, LoadRunner, Performance Testing, Scripting, Vugen
Error: “Cannot install license information, probably access to system resource was denied”
Solution:
This error indicates that you need to log in with local administrator permission, since you installed the product with administrator permission. If you still get the error after login as local administrator, run setlicensepermissions.exe from the \bin directory to change the registry permissions
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, LoadRunner, Performance Testing, Scripting, Vugen
Error: “License manager does not support objects of this type or license is invalid”
Verify the followings:
Check the properties of the license key. If you apply a license key that has components that does not come with that version of LoadRunner, you will get this error.
Example:Apply WAN emulation license (introduced in LoadRunner 7.6), or J2EE diagnostics (Introduced in LoadRunner 7.8 FP1) license on LoadRunner 7.5 Make sure that you are applying the license key on a machine where the license is generated for. In LoadRunner7.x, license keys are host lock. If you try to apply the license key on a separate machine, you will get this error.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, ExtraStuff, General, LoadRunner, Performance Testing, Scripting, Vugen
How do I generate a HostID for a LoadRunner license in load runner
For LoadRunner7.0 – 7.8 Feature Pack1:a. Bring up the Controller and go to Help - About LoadRunner b. Click on ‘License Info…’ and you will see the ‘Host ID’ on the screen. For LoadRunner8.0:a. Go to Start - Programs - LoadRunner - LoadRunner b. Click on the ‘License’ menu and you will see the ‘Host ID’ on the screen. Note: If for some reason you are not able to get to this screen, you can run licidgenerator.exe in \bin directory to generate Host-id
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, General, LoadRunner, Performance Testing, Scripting, Tips n Tricks, Vugen
Bugzilla interview questions?
What is Bugzilla?Bugzilla is a bug tracking system developed at mozilla.org. How do enter a bug in Bugzilla?To enter a bug, through "Enter a new bug" link from the main Bugzilla page. This will take you to a product selection screen. What happens once enter a bug?After you enter a bug, mail is sent both to you and the QA department. A member of the QA department will verify that they can reproduce your bug. How do search a bug?To search a bug, through "Query" link from the main Bugzilla page.
How do submit a patch?The new Bugzilla system supports the attachment of patches, test cases, and various other forms of file types directly from the bug report screen. Just click on "Create an attachment" Are cookies required in Bugzilla?Yes. How can you view your assigned bugs?We can view the assigned bugs though “My Bugs” link. How can you generate bug report?We can generate bug report through “Report” link. When Bugzilla was released?Bugzilla was released in 1998. Which language was written Bugzilla first time?Bugzilla was originally written in "TCL". Who developed the Bugzilla?Terry Weissman
Which language Bugzilla written?"Perl" What are the Bugzilla fields?Bugzilla have 11 fields like- (1)Product (2)Component (3)Version (4)Platform (5)OS (6)Priority (7)Severity (8)Assigned To (9)URL (10)Summary (11)Description
How can you edit your account in Bugzilla?We can use "User Preferences" link. How can you add new Product in Bugzilla?We can use "Product" link for adding new product. How can you add Components of product in Bugzilla?We can use "Components" link for adding components in Bugzilla. How can edit version of any product in Bugzilla?We can use "Edit Versions" link.
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Errors in LoadRunner, ExtraStuff, General, LoadRunner, Performance Testing, PerformanceCenter, Scripting, Tips n Tricks, Vugen
"Memory violation error "in Load Runner
Reasons for this:
C pointer errors,C programming invalid declarations
Memory full
Not enough Memory for what you need to place in a defined space
Memory not yet allocated before attempting to use it
Memory allocated but not deallocated
Trying to copy a non pointer version of a datatype to a pointer defined version of a datatype, such as copying a character array to a pointer to a character array
Generally unless you have a hardware issue this is a developer error
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, Errors in LoadRunner, General, LoadRunner, Performance Testing, Scripting, Tips n Tricks
Sample date conversion program using vugen scripting in Load runner
//Main Function
Action() { char *ConvDate; //Call date conversion function dateConv("10/JUL/2009", ConvDate); lr_output_message("date is %s",ConvDate); return 0; } //Date conversion function
dateConv(char *MyDate, char *ReqDate) { lr_save_var(MyDate,2,0,"Date"); lr_save_var(MyDate+3,3,0,"pMonth"); lr_output_message("Month is %s",lr_eval_string("{pMonth}")); if(strcmp(lr_eval_string("{pMonth}"),"JAN")==0) lr_save_string("01","Month");
/* Similar rest of the code goes here....*/
else if(strcmp(lr_eval_string("{pMonth}"),"DEC")==0) lr_save_string("12","Month"); lr_save_var(MyDate+7,4,0,"Year"); ReqDate = lr_eval_string("{Month}/{Date}/{Year}"); lr_output_message("date is %s",ReqDate); return 0; }
Posted by raviteja gorentla No comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: ExtraStuff, General, LoadRunner, Performance Testing, Scripting, Tips n Tricks, Vugen
Invoke Vugen from a .net app
Steps for running Vugen from a .NET application:
1. Add System as a Reference to the project 2. Here is actual code to run the script - Shell("[Vugen Installation Folder]\bin\mmdrv.exe -usr [Full path of the script] -vugen_win 0", AppWinStyle.NormalFocus) Example :
Shell("C:\Program Files\HP\Virtual User Generator\bin\mmdrv.exe -usr C:\FlightsTool\FlightCal.usr -vugen_win 0", AppWinStyle.NormalFocus) Note: Neither Vugen now the Run Time window will be visible as the script runs in the background, however the results, log files, etc will be still be saved in the usual location.