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

JMeter Exceeded Maximum Number of Redirects Error Solution

While running performance test, JMeter allows maximum 5 redirects by default. However, if your system demands more than 5 redirects, it may result in JMeter exceeded maximum number of redirects error. In this post, we have listed down steps to overcome this error. Actual error in JMeter: Response code: “Non HTTP response code: java.io.IOException” Response message: “Non HTTP response message: Exceeded maximum number of redirects: 5” This error is noticed because  JMeter  allows maximum 5 redirects by default and your system may be using more than 5 redirects. You need to increase this count to more than 5 in jmeter.properties file. Follow below steps to achieve this. Navigate to /bin directory of your JMeter installation. Locate jmeter.properties file and open it in any editor. Search for “httpsampler.max_redirects” property in opened file. Uncomment the above property by removing # before it. Change to value to more than 5 Eg. 20. Save the file and restart JMeter. If
Post a Comment
Read more

SSO with SAML login scenario in JMeter

SAML(Security Assertion Markup Language) is increasingly being used to perform single sign-on(SSO) operations. As WikiPedia puts it, SAML is an XML-based open standard data format for exchanging authentication and authorization data between parties, in particular, between an identity provider and a service provider. With the rise in use of SAML in web applications, we may need to handle this in JMeter. This step-by-step tutorial shows SAML JMeter scenario to perform login operation. First request from JMeter is a GET request to fetch Login page. We need to fetch two values ‘SAMLRequest’ and ‘RelayState’ from the Login page response data. We can do this by using  Regular Expression Extractor . These two values need to be sent in POST request to service provider. Refer below image to see how to do this. We will get an HTML login page as a response to the request sent in 1st step. We need to fetch values of some hidden elements to pass it in the next request. We can do this b
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 and reci
Post a Comment
Read more