Status: Accepted
Owner: ----
Labels: Type-Enhancement Priority-High
New issue 377 by pekka.klarck: Don't convert test suite, test case and
keyword names unnecessarily
http://code.google.com/p/robotframework/issues/detail?id=377
Currently Robot Framework converts test suite, test case, and keyword names
into unified format using these rules:
1) If name has underscores, replace them with spaces (an_example -> an
example)
2) If there were no underscores in the name, add spaces between parts of
camelCaseNames (anExample -> an Example)
3) Capitalize each word (an_example/anExample -> An Example)
This logic works pretty well with library keywords because they cannot have
more natural name than an_example or anExample. With test suite, test case,
and user keyword names converting names automatically like this often
causes different results than expected:
http://code.google.com/p/robotframework-ride/issues/detail?id=205
I propose that we change the logic how names are created like this:
Keywords
--------
- Create library keyword names using the same logic as earlier.
- Keep user keyword names exactly in the format they are created in the
test data. Don't change case, replace underscores with spaces, etc.
- In both cases, match the keyword name used in test cases or higher level
user keywords to available names in case and space insensitive manner.
- Currently also underscores are ignored when keywords are match but I
don't think that's necessary. Not doing that is potentially backwards
incompatible so we need to give this some extra thought.
Test cases/suites
-----------------
- Keep test case name in the same format as it's created in the test data
similarly as with user keywords.
- Get test suite names directly from file/directory name otherwise but
convert underscores to spaces. Using spaces in file/directory names often
causes problems and we want to avoid them.
- When matching test cases/suites (--test/--suite options), keep the match
space and case insensitive.
- I don't think we need to ignore underscores here anymore either.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
