You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if a test suite for example only applies to the Connect protocol, then there will be no Protocol:PROTOCOL_CONNECT element in the permutation name. The logic to create the permutation names attempts to make the names shorter by omitting elements that can't vary. But this can be counter-intuitive for users since it means the names are not always consistent. One would have to examine the test suite data and its properties to determine what the permutation names will look like.
Instead of favoring shorter permutation names, it might be nice if the names always included all properties. This can also make it easier to create patterns for a single protocol, compression, HTTP version, codec, or TLS setting. One could use a pattern like **/Protocol:PROTOCOL_CONNECT/** and be guaranteed that it matches all test case permutations that use the Connect protocol. Whereas today, there may be Connect-only test cases that do not contain that string.
The text was updated successfully, but these errors were encountered:
Currently, if a test suite for example only applies to the Connect protocol, then there will be no
Protocol:PROTOCOL_CONNECT
element in the permutation name. The logic to create the permutation names attempts to make the names shorter by omitting elements that can't vary. But this can be counter-intuitive for users since it means the names are not always consistent. One would have to examine the test suite data and its properties to determine what the permutation names will look like.Instead of favoring shorter permutation names, it might be nice if the names always included all properties. This can also make it easier to create patterns for a single protocol, compression, HTTP version, codec, or TLS setting. One could use a pattern like
**/Protocol:PROTOCOL_CONNECT/**
and be guaranteed that it matches all test case permutations that use the Connect protocol. Whereas today, there may be Connect-only test cases that do not contain that string.The text was updated successfully, but these errors were encountered: