In a recent commit to add test auto-generation, the acronym tests were switched to be auto-generated and in the process the test for CamelCase was lost, seemingly unintentionally:
Since this is the only test for camel case being handled, the tests now pass without handling this case which simplifies the problem a fair amount. I was made aware of this by a mentee asking why other solutions seemed more complicated than his.
It seems like this was an unintentional change to the test cases for the acronym exercise and that this test should be added back in?
My second hunch is that adding this test to problem-specifications probably isn’t the way to go, because it makes the exercise more difficult for languages that implement the existing tests only.
I’m a little hesitant to deviate from the problem spec without good reason. But the confusion about the community solutions will remain. Good enough reason for me.