You could also use Nightwatch default config which would save you from all the configuration
That seems like a silly suggestion.
- it disregards the specific requirements that I have
- it doesn't work. Using the example provided on the docs that I linked, the cli runner still doesn't create any webdriver instances
Additional feedback:
when starting the runner, I don't think it should resolve if there are no instances to start. Rejecting due to no instances would be best, but at least have a warning logged that there are no instances created (and why) would save a lot of time in debugging.
Hi.. I am using nightwatch API as a node service. I found that over the time, the memory is keep increasing. When I profiled the node app, I see the results are not being cleared from memory and all the loaded scenarios as modules are in memory in the form of strings. Is there a way to unload the scenario when a test is completed?
Also is there a way to store the results as JSON file.. I am using the reporter callback in globals to get the results and saving it as JSON. But when there are many tests, the results object is huge and it is crashing the server when saving it to file system (Probably during stringify. I am using BFJ library to stringify the object asynchronously). Any ideas to reduce the report size?
Thanks
var HtmlReporter = require('nightwatch-html-reporter');
/ Same options as when using the built in nightwatch reporter option /
var reporter = new HtmlReporter({
openBrowser: true,
reportsDirectory: __dirname + '/reports/'
});
module.exports = {
write : function(results, options, done) {
reporter.fn(results, done);
}
};
nightwatch --tag accessible --default --reporter ./html-reporter.js
Hi.. I am using nightwatch CliRunner in a nodejs as a service. I am trying to enable the parallel testing by setting
test_workers: {
enabled: true,
workers: "auto"
},
After adding these two, I am getting the message "Started child process for: xxxx.spec.js", but it is failing soon afterwards with error "Address already in use ::: 8081" This address is actually the address of the nodejs server. So is it trying to run the server again?
Is there a way to run the tests in parallel when using this in nodejs server instead of cli tool?
I have a test and fail message
buildPlanPage.assert.containsText('@activeButton','Gravity Only')
Testing if element <Element [name=@activeButton]> contains text 'Gravity Only' in 5000ms - expected "contains text 'Gravity Only'" but got: "does not contain 'Gravity Only'"
Is it possible somehow to have message like
expected "contains text 'Gravity Only'" but got: "real text that element has" ?
--suiteRetries option, my github action runs forever (it sais passed successfully but does not exit). I run it using the following command:xvfb-run --auto-servernum --server-args='-screen 0, 1920x1080x24' yarn test -e local --suiteRetries 3 --verbose. Did any of you ever meet this problem?
1 reply