Skip to main content

Reporting Defect in QTP

Reporting Defect


Defining our own Result in result summary:

QTP has 4 types of result status:

♦  Pass
♦  Fail
♦  Done
♦  Warning


Result is captured using ReportEvent Method:
Generally QTP provides, test results, if we use qtp tool features like checkpoints. Suppose if we use flow control statements (conditional and Loop statements), then we have to define our own result.For defining our own results, QTP is providing an utility object called "Reporter" by using reporter, we can define our own results.
Syntax:
Reporter.ReportEvent EventStatus, ReportStepName, Details [, Reporter]
Arguments:

EventStatus:             Status of the report step.Different types of event status are mentioned below:
0 or micPass:        Causes the status of this step to be passed and sends the specified message to the report.

1 or micFail:         Causes the status of this step to be failed and sends the specified message to the report. When this step
                           runs, the test fails.

2 or micDone:       Sends a message to the report without affecting the pass/fail status of the test.

3 or micWarning:  Sends a warning message to the report, but does not cause the test to stop running, and does not affect
                           the pass/fail status of the test.

ReportStepName:   (String)Name of the intended step in the report (object name).

Details:                (String)Description of the report event. The string will be displayed in the step details frame in the report.


Ex 1: The following example use the ReportEvent method to report a Passed step with different format of  Event  status
Reporter.ReportEvent 0, "User Login", "Passed as the Login functionality worked as per the requirment"
 
'OR
 
Reporter.ReportEvent micPass, "User Login", "Passed as the Login functionality worked as per the requirment"

Ex 2: The following example use the ReportEvent method to report a Failed step with different format of  Event  status
Reporter.ReportEvent 1, "User Login", "Failed as the Login functionality didn't work as per the requirment"
 
'OR
 
Reporter.ReportEvent micFail, "User Login", "Failed as the Login functionality didn't work as per the requirment"

Ex 3: The following example use the ReportEvent method to report a Done step with different format of  Event  status
Reporter.ReportEvent 2, "User Login", "The Login functionality is validated"
 
'OR
 
Reporter.ReportEvent micDone, "User Login", "The Login functionality is validated"

Ex 4: The following example use the ReportEvent method to report a Warning step with different format of  Event  status
Reporter.ReportEvent 3, "User Login", "Warning : No input provided"
 
'OR
 
Reporter.ReportEvent micWarning, "User Login", "Warning : No input provided"
Labels:

Comments

Post a Comment

Popular posts from this blog

Performance Testing in the Cloud with JMeter & AWS

JMeter is a wonderful tool  to stress test your website and  your application architecture , however if you are trying to simulate many users (>1000) one JMeter instance (=pc) will not be sufficient. You will have to set up a JMeter cluster with multiple machines. JMeter is capable or running  distributed tests , but it comes with limitations. Since most of us don’t have multiple servers laying around somewhere, we usually go to cloud service providers like  AWS , spin up a couple of  EC2 instances  and turn them off whenever we’re done. Here is the problem, JMeter uses  Java RMI (Remote Method Invocation)  to communicate to its slaves, but these connections require all machines to be on the same subnet and this is not feasible with EC2 instances. Below, I explain how to get around this problem using a 3 node configuration in AWS to execute tests. I assume that you have a written the test already and have the .jmx file r...
Post a Comment
Read more

Difference Between Redirect Automatically and Follow Redirects in JMeter

In this post, we will highlight important difference between Redirect Automatically and Follow Redirects options. These options are found in HTTP Request sampler of JMeter. Knowing the difference will help you decide your performance test strategy. When you check Redirect Automatically option, JMeter will not consider redirect as separate HTTP request. This in turn may result as lower response time in your overall performance test. Whereas Follow Redirect option will consider each redirection as separate requests. This may result in comparatively higher response time. This only has any effect if “Redirect Automatically” is not enabled. To see the difference between these two, record a sample script and run it by checking Redirect Automatically and Follow Redirects option. The second option will generate more requests in your result listener. As you can see from the above post, knowing the difference between Redirect Automatically and Follow Redirects option makes difference i...
Post a Comment
Read more

A Tutorial to Send Email using JMeter

Sending email is a mundane activity in any professional’s life. It’s a common medium for communication nowadays. Therefore performance testing of email server is not only important but necessary for an organization. JMeter can be helpful to perform load testing in such scenarios. In this tutorial, we will see how JMeter can be used to send email. We will use SMTP Sampler of JMeter to send an email. JavaMail API is needed to enable email functionality in JMeter. Download it from  here  and paste the jar in JMeter’s lib folder. Now, perform below steps to configure SMTP Sampler. Add a new Thread Group under Test Plan. Right click on Thread Group and select Add–>Sampler–>SMTP Sampler. We need to populate SMTP server’s details in this sampler. We will use GMail for sending an email. For this, enter these values in SMTP Sampler fields. Server: smtp.googlemail.com, Port: 587. Provide values in Email Address From and To fields of Mail Settings section to specify sender...
Post a Comment
Read more