We are "successfully" running our gherkin-testcafe build on ec2 headless against chromium. The final issue we are dealing with is that at a certain point in the test a CTA button is showing ...loading instead of Add to Bag, presumably because a service call that gets the status of the product, out of stock, in stock, no longer carry, etc. is failing. The tests work locally of course and we have the luxury of debugging locally opening chrome's dev env and inspecting the network calls etc. But all we can do on the ec2 is take a video and see where it fails. Is there a way to view the logs of all the calls being made by testcafe's proxy browser so we can confirm which one is failing and why? We are using.
const rlogger = RequestLogger(/.*/, { logRequestHeaders: true, logResponseHeaders: true });
to log our headers but not getting very explicit reasons why calls are not working.
from Recent Questions - Stack Overflow https://ift.tt/31XkYXb
https://ift.tt/eA8V8J
No comments:
Post a Comment