Yes, I think so.
Saying “two numbers can be removed” is not accurate. It is more like “remove digits”.
Ah the same is happening for me; my algorithm with only removing zero or one digits solves all test cases, but fails validator 3. While it was said this is not an issue, it seems that at least there is imbalance between test and validator 3 (and, test 3 does not work for requiring the removal of two digits - or technically I am removing two digits, but the second digit is simply removed through int()).
This would be solved if test 3 current input number 104890600 is changed into 114890600.
Missing tags for
-
String
-
Loops
Inconsistency in the different unit tests. Unit tests need to convert to int for in game validation for the 2 digit case, but must be given as a string to pass the final validators. Maybe change the final validation test for 2 digits in order to pass when converted to int ?
hard to understand for me what are you talking about
SUPER poor test cases
I think I’ve found the problem with the remove 2 digits validator; although, I haven’t seen the validator so I can’t confirm. The test case removes both digits from the start, so if the program isn’t removing digits from the middle, the answer can be accidentally found. Furthermore, the 2nd digit being 0 means that a program that removes 1 digit results in the correct answer with a leading 0 so, as others have mentioned, converting to integer accidentally results in the correct answer.
The test case has no inherent problem as it is, so long as it isn’t the only test case for 2 digit removals. A test case should be provided where the digits to be removed are in the middle and, more importantly, the answer can not be found accidentally by removing one digit and leading 0’s.