I have a test collection with hundreds of tests.
I'd like to send the test result as an SMS message on my phone.
I have all the other parts working but is there any way to get a count of passed and failed tests as a variable for my last test which is testing our SMS service, so I could get the result to my phone as an SMS message.
I only need to get a count of failed and count of passed cases during the collection run.
But if it is possible to get the name(s) of the failed cases as well, then I would be fully satisfied.
-Jarno Storhammar-
You could try creating a node script with Newman and sending the results captured in the summary.run.stats object to an external API, that would send you an SMS message with the details you want. Services like Twilio could handle that part.
It's not something the native Postman app would perform out of the box but I'm sure it can be done.
Related
I’m searching for a solution for a following issue:
There is a user-flow (folder with a list of requests with a relevant tests).
User-flow running under Newman + htmlextra ci/cd pipeline
User-flow running on test environments which is has 3 party dependencies (services, networking etc)
The issue is the network timeouts, socket hang up.
Which is why i added a kind of retry mechanism in postman
that allows me to repeat the requests once test got status code 5xx
Print screen: User-Flow report
So eventually the user-flow itself pass as you see at the print screen
(the second retry succeeded) but Newman return fail on such user-flow
once we got at least one timeout.
The question is: How i can overcome such issue
Once the retry succeeded i would like Newman will return Success (exit code 0)
Please see the image :
Just imagine : You are getting 5xx series code on "Code Generation" request and you want to retry until you get 2xx series. use the following code for that.
if(responseCode.code!=200){
postman.setNextRequest("Code Generation");
}
pass the request name in setNextRequest
We are using twilio for sending messages but as Twilio(Text Messaging) integration was shutting down we deployed the integration using cloud run by following steps from https://github.com/GoogleCloudPlatform/dialogflow-integrations/tree/master/twilio#readme
After deployment messages were sending successfully but now suddenly we are getting errors in twilio like
Some messages are sending successfully and for some messages we are getting error.can anybody help me in this.thanks in advance
According to Twillio docs there might be some possible causes for Unreachable destination handset
1.The destination handset you are trying to reach is switched off or otherwise unavailable.
2.The device you are trying to reach does not have sufficient signal
3.The device cannot receive SMS (for example, the phone number belongs to a landline)
4.There is an issue with the mobile carrier
Possible Solutions
The first step to troubleshooting this issue is to attempt to replicate the problems.
Attempt to send another test message to this user via a REST API request, or through the API Explorer in the Twilio Console.
I have created a Talend job and deployed it as a Axis Web Service.
I am calling this Web Service from my Web Application.
My application and web service are deployed over Tomcat server.
For Valid Inputs:
Runs Perfectly.
For Invalid Inputs:
It throws Error/exceptions in Tomcat Server.
I want this Errors into my application. I didn't get any error related information in the Response sent by web service.
Error message on Tomcat Server
XML response of Web service
If I understand your question you are not so much asking how to fix this error, but how to get feedback about your error. There are several ways but here is a simple method.
Add a tLogCatcher to your job, and point its output to a tSendMail component. You can run the output thru a tMap do things like adding HTML formatting. You can also create a joblet with these two components and use the joblet in every job so you do not have to recreate it every time.
The diagram below shows a real simple case where I add tLogCatcher and tSendMail directly to the job. When there is an error it will send me an email with the details. You can use any of the columns in row11, I am only using job and message in my example.
This error : For input string "fabrik"
is generated by the tFileInputExcel component when encountering a non valid field (expected : integer ; given : string). You can't directly catch this error with the tFileInputExcel component (it's just printed out on the console).
However, you can use a tSchemaComplianceCheck component after your tFileInputExcelComponent : it will throw an error if a data is not valid for your schema. This component has a reject link to catch the error.
tFileInputExcel->tSchemaComplianceCheck->tMap->tMSOutput
If you use tLogCatcher component to catch the error then, at the end of the flow, you can add a tBufferOutput component. Keep the fields with the information you want for.
component configuration
The result will be like this (note that they are shown in the same order):
result
I am doing it like this:
Inside OSB pipeline's message flow, at the beginning of request, assign the current time to a variable. Then in the response, use the current time of the response subtract the variable to calculate the response time. Then I have a reporting action to reporting this number.
I know OSB has a build in monitoring tool, it can display the response time for proxy server, pipeline and business server. As you can see my solution only include the time from the beginning of the pipeline + business server, but not including the time of the request and response message going through the proxy server. Besides that calculating it this way also feels like a non-standard approach.
OSB provided a JMX API which can get these build in monitoring data. But this would make our project more complicated.
If we want to use the OSB reporting action to report the response time. Is there a best way to do it?
Just switch Weblogic to use extended log format, and tell it to add time-taken to the list of tokens it logs on each response.
http://middlewaretechnologies.blogspot.com.au/2012/03/configure-extended-logging-in-http.html
or if you want to read the official docs:
http://docs.oracle.com/cd/E14571_01/web.1111/e13701/web_server.htm#CNFGD207
I'm trying to test my WF4 State Machine workflow. A few of the transitions are triggered by Receive activities and, based on the data in the message, make the the appropriate transition. Right now I'm using the WorkflowApplicationTest to run my tests, but am only able to test my timeout pathing, since any other transitions are triggered by this receive. I've looked at using the XamlInjector to mock the Receive, but it looks like it only works with custom activities. I also tried making a custom Receive activity so that I could mock that, but couldn't figure out everything I needed to do to make my custom receive work or find any info on creating custom Receive activities.
Is there a simple solution that I am overlooking on how to test this? And if a custom Receive is the only way to be able to use the XamlInjector, how do I write one?
I am using the Visual Studio test framework for my unit tests.
I've got just the thing for you. See How do I Mock Receive and Send activities?