#1597 closed enhancement (wontfix)
associating files to test cases
Reported by: | anonymous | Owned by: | edunne |
---|---|---|---|
Priority: | normal | Component: | TestCaseManagementPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
It would be nice to associate files from the SVN repository to test cases, so if they were modified, those tests would require revalidation... What do you think?
Nuno Correia nbettencourt _at gmail _dot com
Attachments (0)
Change History (2)
comment:1 Changed 17 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 17 years ago by
By "validating" I meant someone performing the test again, after a change to a file marks it as requiring it.
I thought it would be something like having a <required-file> tag in the test case definition file, then some SVN hook would reopen its ticket if there were tests that had it.
I get your point, but what if rather than relying on a DB model, the definitions were traversed at commit time, looking for those which refer to the file in the rep? Or is that too expensive to the server?
nbettencourt
yeah it's a good idea, except that would require a way to manage that relationship. I've want to avoid any kind of data base model where the relationships would have to be stored.
hence the use of the testtemplates.xml file and having the testid as part of the test case defintion.
for now the testvalidation link will check for correctness of the structure of the testcase.
Or did you mean something else by "validiate". Did you mean have someone else check the content of the testcase?
Anyway, I'll mark this as won't fix for now, but please feel free to add more detail.