UUID is not sufficient for uniquely identifying an individual test. Rather, it identifies a functionality that can be subclassed. However, for Defcore and interoperability testing functionality may not be universally required. For example, IPv4 functions may be required, but IPv6 may not. We would like to discuss options for uniquely identifying tests that is robust through refactoring. Existing solutions such as parent class ID tagging, multiple tags with subclass information, and using test names have been proposed as a solution. The goal will be to identify, document, and possibly implement a solution whether it be in code or in process.
