-
Notifications
You must be signed in to change notification settings - Fork 672
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
Add a separate property for the reporter factory function #6286
Comments
This functionality will be available after we support the JS configuration file. You will be able to load your reporter using the |
Hi! seems js configuration already implemented, is there any guide which shows how can i use my local reporter? |
Hi @mokone91, You can specify your local reporter in the JS configuration file in the following way: .testcaferc.js
|
Hi!
and seems it works as expected, the only point here - I passing reporter as name 🙃 |
It occurred due to the parsing reporting parameters algorithm. It's not part of a public API and can be changed at any time. Please, use the approach from the #6286 (comment). |
Hi @miherlosev But how then I can select multiple reporters and configure outputPath for custom? |
Hi @mokone91 We discussed this with @AndreyBelym one more time and decided the following:
const customReporter = require('./customReporter');
module.exports = {
...
reporter: [
{
reporter: customReporter, <--- new property
output: './reports/e2e_report.xml'
}
],
}
|
Since there is a workaround (using the |
Seems it's not possible to use local reporter using config file now.
Its can be wery useful feature, especially as is possible with js interface.
The text was updated successfully, but these errors were encountered: