-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
fix(#9): cannot start wdio tests #28
Conversation
@christian-bromann, to further improve this PR: |
seems reasonable, do you want to do this in a separate PR or in this one? |
Any idea on how to elegantly get the parsedAnswers in here L188 ? I need to do something like : const relative = path.relative(process.cwd(), parsedAnswers.destSpecRootPath);
const tsconfigDir = relative.split(path.sep)[0];
const wdioConf = {
builder: '@wdio/schematics:wdio',
options: {
devServerTarget: `${project}:serve`,
tsconfigFile: `${tsconfigDir}/tsconfig.e2e.json`,
},
configurations: {
production: {
devServerTarget: `${project}:serve:production`
}
}
} |
Shouldn't it be possible to store data in the |
I don't think so... And anyway |
I won't be able to solve it without making many changes. Running the wizard is optional so I cannot rely on the parsed answers that it returns. I guess the wizard shouldn't be optional (why would it be after all ?) |
Unfortunately I'm acting blindely on this one because I was not able to mount this project locally to make the proper modifications. I followed the $ npx ng add @wdio/schematics
> An unhandled exception occurred: Cannot find module '/Users/badisi/webdriverio-schematics-main/src/schematics/webdriverio/index' |
Fix #9