![]() ![]() You should try to prevent the removal by fixing these RC bugs. It depends (transitively) on nvidia-graphics-drivers-tesla-470, affected by 1011146. ![]() Puts "Time.new(2021, 10, 5, 9, 0, 0, '-07:00')}: #: 0.0004161418930646181Īs you can see these times are not equal and the reason being is there seems to be a 4/10000th of a second discrepancy between the two. Installing ruby-timecop package on Ubuntu is as easy as running the following command on terminal: sudo apt-get update sudo apt-get install ruby-timecop. ruby-timecop Ruby library to easily test time-dependent code. Version 0.9.1-1 of ruby-timecop is marked for autoremoval from testing on Thu. ![]() Given the following rspec test: it 'Testing TimeCop', travel: Time.new(2021, 10, 5, 9, 0, 0, '-07:00') do It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call. I thought it was my code but it seems that I'm getting fractions of a second added somewhere which is causing dates that should be equal to not be. A gem providing 'time travel' and 'time freezing' capabilities, making it dead simple to test time-dependent code. timecop DESCRIPTION A gem providing 'time travel' and 'time freezing' capabilities, making it dead simple to test time-dependent code. I've TimeCop installed and using the travel: option with my tests but my tests seem to be failing when I know they shouldn't be. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |