| Author: | Bianca Jiang |
| email: | bjiang@us.ibm.com |
| Last updated: |
Rough workload estimate for design/code/test in person weeks: 2
Rough workload estimate for doc in person days: 10
Theme:
Component: Test.UI.FrameworkEditors (Test Log
Viewer)
Defect Tracking support from Test Log Viewer
When users see a failed test case in Test Log Viewer, a very useful use case is to allow them submit defect(s)/enhancement(s) for the particular test result (not limited to verdicts, but applicable to any execution event). Later on, users should also be able to get the associated defects with the execution event and be able to further query for the status, details, etc. about the defects.
TPTP should provide the extension point for consuming tools to plug in their own defect tracking system. This will make Test Log Viewer a much more useful tool than just a results viewer.
1. After the users execute a test and see their test results in Test Log Viewer, the next step is to submit a defect or
feature request against the interesting execution event, e.g. failed verdict.
2. Or, if the user knows there are already existing defects for the same problem, they could query for the defects and be able to associate them with the test result.
3. When a user opens an existing Test Log, they want to look at (and maybe modify) the defects that's associated for the results.
For any selected execution event, or the overall execution result, the user should be able to:
1. submit a new record
2. open an existing record
3. query for existing record(s)
When perform any of the above actions, the defect tracking provider should allow users to create a new repository connection
when there's none, or select from the existing connection. The existing connections can come from the consuming tools from earlier
configurations, or they can come from the information stored with the current test log.
4. associate with a record(s)
5. remove the association with the record(s)
Extension point for consuming tools to plugin their own defect tracking support. Here is the java interface.
bugzilla 130574 provide a patch for previous releases to be compatible with new resources with model changes.
Proposed data model design: