-
Notifications
You must be signed in to change notification settings - Fork 30
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
knapsack_pro 7.6.1 fails with RSpec #263
Comments
What does the knapsack pro command look like that you use to run tests? I'm wondering why our integration tests did not catch this issue. Please could you use 7.6.0 before we fix this issue. |
Our pipeline runs |
ArturT
added a commit
that referenced
this issue
Jun 26, 2024
…which means rails_helper is not loaded and knapsack_pro lib is also not loaded. This verifies if the custom KnapsackPro::Formatters::TimeTracker formatter from knapsack_pro can be used before knapsack_pro is loaded #263
ArturT
added a commit
that referenced
this issue
Jun 27, 2024
… in RSpec when using Knapsack Pro Regular Mode and the `.rspec` file is not present. (#265) * update(CI tests): reproduce an issue when the .rspec file is not set which means rails_helper is not loaded and knapsack_pro lib is also not loaded. This verifies if the custom KnapsackPro::Formatters::TimeTracker formatter from knapsack_pro can be used before knapsack_pro is loaded #263 * fix(KnapsackPro::Formatters::TimeTracker): require utils to fix failing tests on CI * Update CHANGELOG.md * run only spec that explicitly requires spec_helper. This is needed when the .rspec file is not loaded with --require spec_helper * reproduce the issue on CI
We've released the knapsack_pro 7.6.2 version that fixes the problem. Please update it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dependabot created a PR on our repo to bump
knapsack_pro
from 7.6.0 to 7.6.1 and our build fails inside KnapsackPro internals, probably due a require that was missed on #262. This is the backtrace we get 👇The text was updated successfully, but these errors were encountered: