Commonly occurring issues

• 🛑 Poor language of the description: The description contains the typo and grammatical error: “yhus, if product 1 has licenses for EU, US and EU again, it must be exactly two migrated versions.” Replace yhus with “thus” and rephrase this as “there must be exactly two migrated versions.”
• 🛑 No debugging info on failure: Submission-test failures do not generally identify the tested inputs. For example, NewIdsStartAfterMaximumOriginalId uses a generic message from AssertMigration, and RandomMigrations reports only Failed randomized test #... rather than the generated products and licenses.
• 🛑 Tests must not reuse potentially mutated inputs: In HandlesLargeInputEfficiently, the mutable products array and licenses list are passed to Kata.Migrate and then reused in assertions such as products.Select(...) and licenses.Select(...). Pass copies to the user solution or compute the expected ID sequences before calling it.
• ⚠️ Tests should be ordered: The submission tests have no NUnit [Order] attributes, so fixtures such as NewIdsStartAfterMaximumOriginalId, RandomMigrations, and HandlesLargeInputEfficiently can run out of the intended fixed → random → large order. Add [Order] to the tests or appropriately separated fixtures.

Please mind that I am not a very smart bot, and you should verify my remarks with any resources available for kata authors and translators:

• Codewars Authoring Guidelines
• #help-authoring channel of Codewars Discord
• Authoring examples
• Collection of authoring examples