Well… I wanted to add to the request and did some research to make a good suggestion how this can be handled… And found out it’s already implemented.
When you decompile the “Keyword” annotation it shows you that it has a method:
public abstract java.lang.String keywordObject() default "General";
Since i saw that it defaults to “General”, which is the folder where all custom keywords are placed in… I concluded you could probably use this.
If you include the “keywordObject=…” in your annotation you can at least create a folder structure that is one level deep:
@Keyword(keywordObject = "Test")
Sadly, you can’t implement any folder hierarchy, neither with slash (becomes part of the name) nor with backslash (compile error - unexpected character) nor with escaped backslash ( \\ -> see picture, becomes part of the name as well):
Annoyingly, the Keywords Browser only updates when you close and reload the project. It also doesn’t really help you with easier manual test case editing, since the dropdown list for custom keywords still include ALL keywords sorted as if in one folder.
It’s actually quite irritating that none of the developers were able to answer with this information?!
Still, the feature is nearly there, it’s just not finished and thought through. I can’t see how people with hundreds of custom keywords (using the POM) are really productive with the current solution.