Closed bheemreddy181-zz closed 4 years ago
I am unable to recreate the problem. Can you create a sample project that reproduces the problem and share it?
The timestamp is generated by a call to Time.now.to_i.to_s
. Are you using timecop or mocking Time.now in your tests? Is the time correct on the machine you using to generate the coverage report?
Thanks @jessebs it is because of the Timecop.freeze. It's working fine now.
The timestamp generated in report header seems wrong