In the task n is said to be in range [3, 30], but random tests have examples with n==1.

Lack of small preloaded tests, especially tests on arrays.
Debugging huge random tests is quite a pain.

what about the possibility of having a list as first layer? (note: it would need a slight change in the description)

{..., '2': []} should equal {..., 2: []}

This behavior isn't specified in the description (and is highly arguable): the original key was an int, but it hasn't been converted to a string in your solution. For now it's undescribed, but moreover, that sounds inconsistent to me (because if the first key is an int and you find another layer below, it will be cconverted to a string. So for homogeneity purpose, all keys in the output should be strings).

Side note: currently, the way the test suite is splitted (is it even splited..?) isn't correct: everything appears in a "random tests" block. => ?
Some readings you might find useful: https://github.com/Codewars/codewars.com/wiki/Codewars-Python-Test-Framework-V2

Hi,

Unfortunately, that's a duplicate of an old kata (which is JS only, that's why you didn't find it... if you searched for duplicates... x) ). Moreover, it would need:

• random tests
• tests with keys longer than 1 char (not really important, but...)
• what about empty dicts or empty lists on the way? => the description is missing the info that it won't happen or those become values of the final dict and the edge case is missing

Because of the "duplicate" problem, you should unpublish yours. You can still train your authoring with it, but don't expect it to be approved. The better way would be to translate the other one (tho, that woul dneed to handle some things in there: iirc that kata has some issues)

cheers.