This is just beautiful

Input range should be specified: there can be potential performance requirements, but it is not clear whether it exists based on what's given.

and an array with floating-point numbers

No, that's a horrendous idea. Everyone in every competitive coding site will have a problem with you if you do this.

I think, at this moment only integers is correct input. I`ll add a test case for negative numbers

I suggest including additional test cases, such as an empty array, an array containing negative numbers, and an array with floating-point numbers. Alternatively, you could explicitly mention in the description that these types of inputs are not permitted.

thank you! fixed

Great kata! The only minor issue I encountered was mis-casing of dateOfbirth property (proper camelCase would be dateOfBirth).

fixed

Tests and kata description have been updated! Now we expect to get null if:

• the resource being sought is a natural resource
• there is no corresponding recipe in our collection
• the requested amount is less than or equal to 0"

(I'd keep arguing but I don't think I would be adding any value. I don't think you're providing any reason for why this static function should be wrapped in a class)

yes, I've removed all rounding hacks and all tests are passing now

rounding issue seems fixed

You sometimes expect empty natural resources rather than an empty list (note that expected and actual are switched)

expected: {"time":0,"raw":{"copper-ore":0,"iron-ore":0}} to deeply equal {"time":0,"raw":{}}

actual and expected and switched in random tests

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