You cannot name modules the same as any of the Ranorex class names. So, Validate, Delay, TestCase, etc., are all forbidden, and you will get errors if you try to compile with it.

You should be naming your modules better anyway. For example, what are you validating, what are you delaying?

ValidateOKButtonDisplayed or ValidateProductPrices
Delay500ms or DelayUntilOKButtonAvailable

This will make it easier for people in the future to understand what the module does without having to open it.

Naming things is the hardest thing any programmer does, by far. You need to take time and think about what to name things, it will make a big difference later on when you have to come back and reuse modules.

This is also true in other development projects besides Ranorex tests.

krstcs wrote:...You should be naming your modules better anyway. For example, what are you validating, what are you delaying?..

Thanks for the advice krstcs, I agree fully and do use specific names for modules. In this instance I was setting up a quick solution to experiment with the use of custom reports - it wasn't actually going to test anything. All I wanted was a single module with a small delay so that I could run it in a couple of seconds and view the Ranorex reports.

Thank you for this feedback. I was able to reproduce the issue on my machine. I added an entry to our internal bug tracking system. It would indeed make sense to prevent using module names which are already in use by Ranorex.