The description says "The method only needs to be able to convert positiv[e] numbers", however one of the test cases in the Java version tests for 0, which is not a positive number. The description should be updated to say that the method does not need to be able to convert negative numbers.

My goal one day was to find the 6 kyu kata with the lowest favorability rating and solve it. I did solve it and can't understand why the rating is so favorable at ~60%. The lack of details on the expected formatting (gaps in the result) makes this a much more complicated task than it has to be. I'd say the guesswork on embedded spaces itself is about a 4-5 kyu problem. Since you must complete the easy 6 kyu problem and a sinister documentation problem, this is two challenges warranting a higher complexity rating.

I recommend adding more test cases that attest to the intended output with some meaningful variability in the inputs. I also recommend stating the requirement that the lines in the output follow a rule of fixed width with alignment of the least significant digit in the three columns.

Thanks, must have missed that.
Corrected it now.

The Returnstring has been corrected, but the Visualize portion still says 8E3 is the result.

Its so freaking hard to adjust to this useless spaces after '=' and others...

Thanks for the advice. I hope a loop of 20 ist enough.

Thanks for your tests. I solved this.

Suggest it might be better to put lots of them in a loop instead of just 3 random tests

It looks like your reference solution is always printing your "remainder" part in a field of width 2, but also with a leading space (after the "R").

This means if the remainders are all single digits you are going to get double spaces after "R" instead of single spaces. I doubt this was intentional.

For example. For 273 your solution will give:

273/16=17 R  1
 17/16= 1 R  1
  1/16= 0 R  1
Result=111

instead of (single spaces after "R")

273/16=17 R 1
 17/16= 1 R 1
  1/16= 0 R 1
Result=111

Cases like this are not being tested

.

I included random tests

Thanks, my mistake, have korrekted it

No random tests

Huh? 1000 decimal as hex is 3E8 not 8E3 as in the description/test case