-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Question: Any plans on adding allure reporting? (or any other reporting mechanism) #6
Comments
Maybe you forgot to rebuild the Docker image? I don't have plans to add additional packages to the blueimp/wdio Docker image. The purpose of this project is more like a starter kit, so it's recommended to fork it and create your own Docker Hub Automated build if you require additional software inside the Docker image. So if you make changes to the Dockerfile, you should build your own image, e.g.: docker build -t YOUR_USERNAME/wdio . Then in docker-compose.yml, replace Also, the Allure exports.config = Object.assign({}, require('./hooks'), {
// ...
reporters: [
'spec',
[
'allure',
{
outputDir: 'reports/allure',
disableWebdriverStepsReporting: true,
disableWebdriverScreenshotsReporting: true
}
]
],
// ...
}) |
oh, I see. |
add custom commands
I tried added
@wdio/allure-reporter
to the npm global install list in Dockerfileand added the config in wdio.conf.js
Here's the error I get
Thoughts on what I'm doing wrong?
The text was updated successfully, but these errors were encountered: