Skip to content
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

Improve warning detection in output #122

Open
roberts1000 opened this issue Mar 9, 2024 · 0 comments
Open

Improve warning detection in output #122

roberts1000 opened this issue Mar 9, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@roberts1000
Copy link
Owner

Some projects use the rspec_starter gem to further control how rspec is started. The rspec_starter gem can run other commands that execute before rspec starts and those commands many trigger warning messages. rspec_n currently isn't catching those warning messages so it doesn't show a yellow (Warnings) flag in the results table. They're visible in the individual rspec_n_itermation.* files so it should be possible to expand the logic that's searching for warnings. The same problem would likely occur when the -c option is used to create a custom compound command. If one of the commands, that runs before rspec starts, throws a warning, rspec_n would likely miss it.

@roberts1000 roberts1000 added the bug Something isn't working label Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant