Comment #12 on issue 688 by bryan.oakley: would like to be able to associate metadata with a test case
http://code.google.com/p/robotframework/issues/detail?id=688
I know all this about version control. You're missing the point. Some of this can be done with version control, but that's just one aspect of the ways we might use metadata. I picked that as an example because I thought people could grasp how using tags might not scale as well as the metadata solution.
And yes, I could spend a lot of effort writing a tool that looked at a file, got a diff of the previous file, parsed through the diffs looking for the introduction of a new test case, figuring out which user make that change, figuring out which team that user was on at the date of the change, etc. That would be onerous, and frankly, would crash our accurev server with all the activity (sad fact of life, accurev doesn't handle heavy loads well).
This isn't practical, and can be solved trivially by the introduction of testcase metadata. Hence, my suggestion.
If it goes against the fundamental design of robot, so be it. I thought it would make a nice addition to the feature set, personally. There are all kinds of uses for random key/value metadata. Obviously you (the metaphorical "you", not you personally) see some value because there is test suite metadata. I'm just asking to extend that feature to the test case level.
