Closed m-linner-ericsson closed 1 year ago
I agree. Consistency aside I think we should have good reasons for forcing extra levels of events that don't add any extra information. One could argue that it's beneficial to keep the number of event types you can link to down so that there's only one way of doing things ("what to communicate is volitional; how to communicate it is not"), but IUT can link to a couple of different types anyway, and a CD target might in turn link to other CDs so any query or other code that traverses the graph to e.g. find the underlying source change events would have to non-trivial anyway.
Comments from the 2023-01-19 protocol workshop:
Description
We have an inconsistency that should either be explained or changed:
CLM allows to SUBJECT link to CD, ArtC, as well as SCC and SCS
TCT link Item Under Test (IUT) only allows CD or ArtC as targets, enforcing an extra CD with ELEMENT link to use SCC as IUT when running tests on source code.
Motivation
Confusing why you can set a confidence level on for example a SCS event but you can't use the same event as a IUT link
Exemplification
You can run test on source code and then put a CLM without having to introduce a CD
Benefits
More logical protocol
Possible Drawbacks
None that I can think of