Closed alexander-warner closed 4 years ago
I'll take a look at it. I am assuming the * is only affecting the wdio-html-reporter?
thanks Rich
On Tue, Feb 25, 2020 at 4:47 PM alexander-warner notifications@github.com wrote:
Depending on test execution order, sometimes the Describe with an asterisk will cause the whole report to fail to generate.
describe('test2 * yep', function () { fit('test fit', () => { console.log("made it2"); }); });
Please let me know if there was a way to see an error message. (It took like 40 hours to chop our tests down to finally find the cause.)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/rpii/wdio-html-reporter/issues/19?email_source=notifications&email_token=AEABIEJO2QVVXAOVSWVG7UTREW3X5A5CNFSM4K3YWJS2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IQIICYQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEABIEP3Q4WQ5MDL6U7ZGHTREW3X5ANCNFSM4K3YWJSQ .
Oh, like, is webdriverio and the tests running? Yep. Thanks!
I didnt have any success replicating this. Is it only happening in the mocha ui mode TDD? Any chance you could create a small test that replicates it?
Interesting, the code clip I put above was the entire spec.js file that I ended up using to reproduce it before posting here. I'll try creating a new project and limiting which npm packages are installed. Some general notes: -we are using jasmine -this is a package.json i last tested the above spec file with:
{
"name": "webdriverio-test",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {},
"keywords": [],
"author": "",
"license": "ISC",
"devDependencies": {
"@babel/preset-env": "^7.8.4",
"@rpii/wdio-html-reporter": "^0.8.6",
"@types/jest": "^24.0.23",
"@wdio/cli": "^5.13.2",
"@wdio/dot-reporter": "^5.13.2",
"@wdio/jasmine-framework": "^5.16.15",
"@wdio/local-runner": "^5.16.15",
"@wdio/selenium-standalone-service": "^5.16.10",
"@wdio/spec-reporter": "^5.16.11",
"@wdio/sync": "^5.16.15",
"axe-core": "^3.4.0",
"chromedriver": "^77.0.0",
"jest": "^24.9.0",
"jest-html-reporters": "^1.2.1",
"wdio-chromedriver-service": "^5.0.2",
"date-and-time": "^0.12.0"
},
"dependencies": {
"jquery": "^3.4.1",
"log4js": "^6.1.1"
}
}
Here is a minimal wdio.config.js file - let me know if i should make it more minimal somehow:
const { HtmlReporter } = require("@rpii/wdio-html-reporter");
const log4js = require("log4js");
exports.config = {
runner: "local",
specs: [
"./tests/user-administration-specs/**/*.js"
],
exclude: [],
maxInstances: 1,
capabilities: [
{
browserName: "chrome",
"goog:chromeOptions": {
}
}
],
logLevel: "info",
bail: 0,
waitforTimeout: 10000,
connectionRetryTimeout: 120000,
connectionRetryCount: 3,
services: ["selenium-standalone"],
framework: "jasmine",
reporters: [
"spec",
[
HtmlReporter,
{
debug: true,
showInBrowser: false,
useOnAfterCommandForScreenshot: false,
LOG: log4js.getLogger("default")
}
]
],
jasmineNodeOpts: {
defaultTimeoutInterval: 90000,
},
beforeSuite: function(suite) {
},
};
thanks that should be enough to get the ball rolling Rich
So I was looking at this and I cant make replicate the issue... Any other ideas?
Did you check that it actually created a report? I still see empty directories created - even on the 1.0.3
windows os btw
needed to encode suiteUid and cid to avoid invalid file names
Depending on test execution order, sometimes the Describe with an asterisk will cause the whole report to fail to generate.
Please let me know if there was a way to see an error message. (It took like 40 hours to chop our tests down to finally find the cause.)