Changed all cases of test.assert_equals to test.expect, because i genuinely didnt know how to get rid of that false should equal true at the end

When tests fail, assertion message could be slightly improved. The part "Expected True but got False" is superfluous and potentially confusing, and information about tolerance is missing. MAybe you could check if using test.expect with a fully customised assertion message, including input values, expected values, actual values, and tolerance, would give a cleaner feedback on failure?

forgot to tick the resolve issue box whoops

so use normal brackets instead of square ones right? understood

issue resolved

A known number of values with entirely different meanings should be represented as a tuple, not an array or a list. Use appropriate datatypes!

Do not ask for rounded results. This is documented.