I did NOT see below request in my webtest, however it is being executed and failing.
I know this is a coding issue and it has to be fixed by development team , however I want to skip running this request for now and make my test pass. Please help me.
GTE https://www.corteva.com/etc/designs/default.css
Webtest:
Results:
You can set Parse Dependant Requests to false for corresponding request (e.g. https://www.corteva.com).
Ignore unimportant errors in web test
Related
I'm running on Windows 10 with the latest version, 7.21.1. I imported the example collection featured in their documentation - https://learning.postman.com/docs/postman/collection-runs/building-workflows/. I run Request 1 in the collection through the Runner and Request 4 does not trigger as it seems it should. It is setup in Tests and seems correct based on their documentation. I have my own collection I was trying this with, but when it was not working I then tried this sample and realized there was something else amiss.
Any assistance would be helpful! I can provide more information if needed.
This is what the example collection has in Request 1 under Tests: postman.setNextRequest('Request 4');
Thanks!
I figured this out. I didn't understand the flow of how the operation worked or the flow of runner. All requests that could be called next need to be selected in runner. And this operation works like a goto where all requests after the request that is run next all run. Closing this out.
I’ve been working for about 2 years developing full stack apps (which were fairly mature when I get to them initially) and am starting up my first from scratch. I spent the day spinning up an EC2 instance, loading the dependencies for my stack (Postgres, golang, react), and all the other frills a shiny new machine needs (tmux, npm, vim plugins, git integration etc). I’m now stuck.
I used create-react-app to get started on my front end and running npm start to have a build going. To see this, I can go to my instanceip:3000.
I created golang server code which is serving up on port 8080 and I can hit my helloworld code by going to instanceip:8080/hello.
I added an axios call in my react code to get endpoint /hello which returns a 404.
I also attempted to make my golang handle the index.js as a static page for the instanceip:8080 and that returns a 404.
How do I get my different ports to play nice? I can’t figure out what I’m missing here.
Here’s a snippet of my server code in main:
indexLoc := os.Genenv(webRootEnv) + "/index.html" // verified this is the correct path to my static index.html file by logging it out
fs := http.FileServer(http.Dir(indexLoc))
http.ListenAndServe(":8080", nil)
http.Handle("/", fs)
Anyone have any ideas what I’m missing? Thanks in advance!
There are two things that could be the cause:
You're giving a file name to http.Dir, which expects a directory.
Your handler is registered after calling ListenAndServe, thus making it useless (http.Handle is never called)
You could fix it by changing your code like this:
indexLoc := os.Genenv(webRootEnv) // webRootEnv is a directory path
fs := http.FileServer(http.Dir(indexLoc))
http.Handle("/", fs) // register handler before listening
http.ListenAndServe(":8080", nil)
You might also want to handle the error returned from ListenAndServe to prevent silent failures of your program
Sitecore Experience Optimization Page Testing.
I am trying to test created simple page in Experience Optimization. Locally everything working fine. When i tried same steps in Azure environment it giving me errors like below.
HTTP400: BAD REQUEST - The request could not be processed by the server due to invalid syntax.
(XHR)POST - https://mc-4b5a2ea8-f571-4c60-bf02-50220a-cm.azurewebsites.net/api/sitecore/Settings/SetUserProfileKey
HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request.
(XHR)GET - https://mc-4b5a2ea8-f571-4c60-bf02-50220a-cm.azurewebsites.net/sitecore/shell/api/ct/ItemInfo/GetByUri?datauri=sitecore%3A%2F%2F%7BED7C2C82-114C-4FB1-96A7-6CCF1F37317B%7D%3Fver%3D2%26lang%3Den&_=1518266879976
HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request.
(XHR)GET - https://mc-4b5a2ea8-f571-4c60-bf02-50220a-cm.azurewebsites.net/sitecore/shell/api/ct/ItemInfo/GetByUri?datauri=sitecore%3A%2F%2F%7BED7C2C82-114C-4FB1-96A7-6CCF1F37317B%7D%3Fver%3D2%26lang%3Den&_=1518266879972
Please check attached screenshots for same.
Update for All viewers.
Thanks to #Pete Navarra for answer.
This is a stretch... But I think you are hitting the URL max length, with the length of your domain name. Can you shorten your machine names?
I will try and keep you update on same.
I am trying to load test Nginx installed on an EC2 instance via Jmeter, Everytime I try to load test, only 50% request are successful,
For Eg:
If I try with 10 users, only 5 response are OK
If I try with 100 users, only 50 response are OK
If I try with 500, only 250 response are OK
Any Idea, regarding this strange behavior?
This sounds weird. I would recommend the following troubleshooting techniques:
First of all always check jmeter.log file, it should contain enough information to get to the bottom of your test failure(s).
If JMeter log file doesn't contain any suspicious entries next step would be checking response messages using i.e. View Results In Table and/or View Results Tree listener. This should provide you some high-level information and trends, i.e. you will be able to see if some particular sampler(s) is(are) always failing.
If above steps don't give enough clue to resolve your issue you can temporary enable saving of request and response data to see what is wrong with the failing sampler(s). Add the next lines to user.properties file (located in JMeter's "bin" folder)
jmeter.save.saveservice.output_format=xml
jmeter.save.saveservice.response_data=true
jmeter.save.saveservice.samplerData=true
jmeter.save.saveservice.requestHeaders=true
jmeter.save.saveservice.responseHeaders=true
jmeter.save.saveservice.url=true
and next time your run JMeter test the .jtl results file will contain all the relevant data which can be analyzed using aforementioned View Results Tree listener. Don't forget to revert the change once you fix the script as JMeter listeners are very resource intensive per se and above settings greatly increase disk IO and it may ruin your test.
If none of above helps - check logs on the application under test side, most probably you will get something from them.
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