-
Notifications
You must be signed in to change notification settings - Fork 240
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
Rspec 2.7 total time is wrong #61
Comments
That's because you're using Spork, and since the start time is now registered before code is loaded (in the Edit: Just made a comment on the commit that introduce this: rspec/rspec-core@fd04952#commitcomment-655593 |
@rymai - thanks for bringing this to my attention. I need to give some thought to it, as I think it's important to include the time it takes rspec to load in the total time in a non-spork environment. @Nerian - as a workaround until we get this sorted out, you can set |
Thanks for the temporary workaround David! I too think that's "important to include the time it takes rspec to load in the total time in a non-spork environment". :) |
@Nerian, @dchelimsky - the issue has been reported in rspec-core. |
@dchelimsky - Thanks! I did need to change it to: |
@Nerian - keep in mind that that is not intended to be a public API, and that it's possible this will break with the next release when we come up with a real solution. Should keep you going in the mean time. |
Hi, This issue is now fixed, thanks all! |
Hi,
With the new release of RSpec 2.7 the total time calculation has been modified:
Provide more accurate run time by registering start time before code is loaded (David Chelimsky)
https://www.relishapp.com/rspec/rspec-core/docs/changelog
Check the Finished in *** seconds in the following code. It is calculated from the time guard was started. It doesn't reflect how much the actual test took to run.
The text was updated successfully, but these errors were encountered: