thank you! fixed

rounding issue seems fixed

It should be fixed! Please, test it and let me know.

No, no rounding, please, you just use approximite equality instead

Thanks for this issue!
I intend to revise the task description and include a note specifying that the resulting values should have a maximum of 2 decimal places to prevent the occurrence of extended floating-point values in random tests.
do you agree?

I'm seeing this too in the expected time:

expected { time: 8.7, raw: { 'heavy-oil': 87 } } to deeply equal { time: 8.700000000000001, raw: { 'heavy-oil': 87 } }