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
Hello @gravityvi, I start with the auto-generated one so I put only the chrome part :
chrome: {
desiredCapabilities : {
browserName : 'chrome',
'goog:chromeOptions' : {
// More info on Chromedriver: https://sites.google.com/a/chromium.org/chromedriver/
//
// This tells Chromedriver to run using the legacy JSONWire protocol (not required in Chrome 78)
w3c: true,
args: [
'--load-extension=/home/john/Dev/Liberty/libertyGC'
]
}
},
webdriver: {
start_process: true,
server_path: '',
cli_args: [
// --verbose
]
}
},
when i'm using ES6 Async Await and calling "waitForElementVisible" if the element is not found, the test continue to execute, the function is not throwing an Error to stop the test.
browser.waitForElementVisible(selector, timeout); it work as expected, fails the test and skip the other ones
await browser.waitForElementVisible(selector, timeout); the test continue and ignore the flag of 'abortOnAssertionFailure'