-
Notifications
You must be signed in to change notification settings - Fork 11
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
Exclude option #5
Comments
It'd be cool to enable that, and 'fail on error' option as well, just like the options for 'protractor-console-plugin'. Then this plugin would be superior both in terms of cross-compatibility and the looks. |
@dinvlad Have a look at protractor-fail-fast for "fail on error" behavior. Noted on the exclude behavior. I'll try to have a look at that soon. |
Yes, the fail-fast plugin could help but unfortunately it seems to be targeted for Jasmine. I use protractor-cucumber-framework instead, so it cannot be applied (or I just don't know how). Thanks! |
I see, that's too bad. I guess that firmly establishes that fail-fast behavior belongs outside of this library since there are many different test runners to account for. |
Would be nice to be able to exclude known issues from output, as in original protractor console plugin. For example:
{
package: 'protractor-console',
logLevels: ['severe, warning'],
exclude: ["some nasty bug or warning"]
}
The text was updated successfully, but these errors were encountered: