-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No test names are being set, undefined
instead
#241
Comments
@christian-bromann ? |
Must be with one of the last versions. I discovered the error looking at MochaJS jobs and they have defined this package as |
This might be related to the karma version they are using, the issue doesn't happen when I look at the current tests in this project |
I'll see if I can figure this one out in the coming days |
I created a patch for my setup --> webex/webex-js-sdk#2032 // node_modules/karma-sauce-launcher/dist/reporter/reporter.js
- const status = result.success ? '✅' : '❌';
+ const status = result.success ? '✅' : result.skipped ? '➖' : '❌';
browserData.results.push({
status: 'info',
- message: `${status} ${result.fullName}`,
+ message: `${status} ${result.fullName || result.description}`, |
@taymoork2 would you mind creating a PR? |
@christian-bromann can do - log.info(`Check if 'log.json' for browser '${browserName}' has already been stored.`);
+ log.debug(`Check if 'log.json' for browser '${browserName}' has already been stored.`); |
🎉 This issue has been resolved in version 4.3.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
It seems like with the latest version of Sauce Launcher all results are being transmitted as undefined, see https://app.saucelabs.com/tests/62eaaf74c9244092b878a6d71074992f
The text was updated successfully, but these errors were encountered: