We attach task recorder output to a test run execution attachment (locked down) to give a verification of the actual steps performed during a test. This attachment cannot be changed after a run is complete. However, if the task recording is too large to fit as an execution attachment, we revert to attaching it to the general attachment for the test run. This appears to have no audit trail history available and would permit modification to the attachment much after the test is executed without any indication it occurred other than a timestamp on the attachment creation that is suspiciously later than the test execution event.
- Is there (can there be) auditing on these attachments like there is for any other ADO work Item?
- Can there be improvements made to allow for larger file attachments to the execution attachment?

Report
All responses (
Answers (