Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
I think I did this? If you still see sample tests with code not compatible with Scala 3, then click the RESET button in the trainer to get the latest version (back up your solution first, because it wil also get reset).
If you think there's still some problem with tests, let me know.
Approved. Thanks!
Please see this kumite: https://www.codewars.com/kumite/624a23b422c35400570f83f3?sel=624a23b422c35400570f83f3 with fix for the issue, and migrating tests to Scala 3 (see https://github.com/codewars/runner/issues/89#issuecomment-939592547).
That bothered me too but an experience can be thought as valid when this experience can be repeated some numbers of times though I must agree that I don't have your wisdom.
This problem in ScalaTest is indeed very annoying, and not very widely known. It always annoys me that I need to remember about it when writing Scala tests, and I wonder if it could be avoided or made clearer. But what actually bothers me (a bit) is how quickly a valid issue got closed without fixing because "works for me". 605 other Scala users were just lucky.
@Unnamed: thanks!
@hobovsky: I am not the Scala translator who, unfortunately, has left CW. The probability to have several identical name is small but certainly not null:-(
The random tests generate test names (
it("<name>")
) dynamically. When there are multiple identical names, this is probably when this error appears.Well, I think you just resolved a valid issue without fixing.
Theres a special attention needed when writing tests for Scala, and the error is most probably caused by incorrect setup of tests.
I cannot check atm, but I will verify when I'm back home and submit a fix or reraise the issue if necessary.
I tried several solutions and all worked fine.
I also tried your solution. I didn't get what is in your post but
Sorry, I don't understand why you got