python translation:
https://www.codewars.com/kumite/5e944c70ff41200012757753?sel=5e944c70ff41200012757753
In Preloaded. Fork a solution and you can see it.
Preloaded
.
It's undocumented; you have to run across it somehow, sometime.
So now you have! :]
Thank you, I have changed that. I did not know that assertDeepEquals existed.
*rectangles
Please do not use assertSimilar for comparing Arrays ( or Objects in general ). Use assertDeepEquals.
assertSimilar
Array
Object
assertDeepEquals
Thank you!
Approved
How did you define "usercode" in your tests to check the solution for the symbols and function?
No need to be rude. I was not too lazy to do my job and have searched if there is a kata like this. None came up to do this conversion.
Unless you forbid the native method, this is too thin a wrapper to make a kata.
Also, do a search and see if this hasn't been done before. My guess is it has, but I'm too lazy to do your job.
Loading collection data...
python translation:
https://www.codewars.com/kumite/5e944c70ff41200012757753?sel=5e944c70ff41200012757753
In
Preloaded
. Fork a solution and you can see it..
It's undocumented; you have to run across it somehow, sometime.
So now you have! :]
Thank you, I have changed that. I did not know that assertDeepEquals existed.
*rectangles
Please do not use
assertSimilar
for comparingArray
s ( orObject
s in general ). UseassertDeepEquals
.Thank you!
Approved
How did you define "usercode" in your tests to check the solution for the symbols and function?
No need to be rude. I was not too lazy to do my job and have searched if there is a kata like this. None came up to do this conversion.
Unless you forbid the native method, this is too thin a wrapper to make a kata.
Also, do a search and see if this hasn't been done before. My guess is it has, but I'm too lazy to do your job.