GRme-zz
commented
7 years ago I tried debugging a little bit more. Maybe it's a bug with the Expect?
I set my global timeout to 20 seconds:
const {defineSupportCode} = require('cucumber');
defineSupportCode(({setDefaultTimeout}) => {
setDefaultTimeout(20 * 1000);
});And now I have a following Expect check:
client.expect.element(myElement).text.to.contain(myText).after(10000);
In my case myElement can not be found in DOM to produce an error. But now I get the error message Error: function timed out after 20000 milliseconds, but I exprect that the test fails after 10 seconds because the element myElement can not be found in DOM.
After that I tried to replace the Expect API method with Nightwatch Command:
client
.waitForElementVisible(arrivalDepartureDate, 10000)
.assert.containsText(myElement, myText);And now I get the right error after 10 seconds ERROR: Unable to locate element: ".Grid__colM3___EyfpA" using: css selector.
It's a workaround to forgo Expect, in my case now I have two commands to check element and their text. With Expect I can do it both in one line command.
mucsi96
I'm submitting a ... (check one with "x")
Current behavior I work with Nightwatch-Cucumber and the PageObject Pattern and I get an unexprected "Error: function timed out after 60000 milliseconds".
Expected/desired behavior All Nightwatch-Cucumber checks (like visibility checks) have to fail and no timeout problem has to occur.
Reproduction of the problem As pre-conditions I set the default timeout (60 seconds) globally in timeout.js:
...and I set the
waitForConditionTimeoutandwaitForConditionPollIntervalfor Nightwatch innightwatch.conf.js:Now I have a Cucumber test that has to fail. So, I want to test the right behaviour of the testframework:
And here are the two step definitions:
And here is the page object function for first cucumber step (
detailsPageView.js):...and the page object function for second cucumber step (
bookingStepOnePageView):Now if I will run my test I expect that the second cucumber step will fail, because the first page of booking funnel is not loaded and present. So, the visibility check in booking page object function
client.expect.element(offerSummary).to.be.visible.after();has to fail. Now I expect that the defined"waitForConditionTimeout":30000innightwatch.conf.jswill use in that case and the visibility check will fail after 30 seconds, but I get a timeout error after 60 seconds how it is defined intimeout.jswithsetDefaultTimeout(60*1000).And additionally my test run (test process via
nightwatch --env chrome) doesn't end and the browser window doesn't close. So I have to end the run (process) manually withctrl + c.Here you can see the output:
On last line you can see the
^Cas my manually stopped test process.Especially when I want to execute a test suite with maybe two cucumber tests. The first test is the one I explained and the second is a one where I expect a
pass. In this case both tests will fail for me, because in the second test the visibility check of the first test (client.expect.element(offerSummary).to.be.visible.after();) will fail and I don't know why.This is my console output for both tests (the second one has to pass!):
What is the expected behavior? Please see Reproduction of the problem
What is the motivation / use case for changing the behavior? Maybe my tests will fail and the worst thing is that my test process doesn't end or keep going on with the next cucumber tests.
Please tell us about your environment: Mac OS X 10.12.5 Chrome Browser 59.0.3071.115 npm 5.0.4
npm ls nightwatch cucumber nightwatch-cucumber && node --versionI hope you can help me :)
Thanks, Martin