Is your feature request related to a problem? Please describe.
Within a single test (including all hooks like BeforeEach and AfterEach), I want to be able to consistently identify that all actions belong to the same test throughout its entire lifecycle. This will make it easier to manage and configure shared data in the Suite.
Describe the solution you'd like
One approach is to add a UniqueID() method to provider.T that returns the Suite method’s name. An even better option would be to return a hash of the method name, to avoid the temptation of relying directly on the method name itself through this UniqueID() method.
Describe alternatives you've considered
A possible workaround for now seems to be extracting the method name from t.RealT().Name(). The problem with this approach, however, is that the extraction can be unreliable since hooks modify the returned value.
Is your feature request related to a problem? Please describe.
Within a single test (including all hooks like
BeforeEachandAfterEach), I want to be able to consistently identify that all actions belong to the same test throughout its entire lifecycle. This will make it easier to manage and configure shared data in the Suite.Describe the solution you'd like
One approach is to add a
UniqueID()method toprovider.Tthat returns the Suite method’s name. An even better option would be to return a hash of the method name, to avoid the temptation of relying directly on the method name itself through thisUniqueID()method.Describe alternatives you've considered
A possible workaround for now seems to be extracting the method name from
t.RealT().Name(). The problem with this approach, however, is that the extraction can be unreliable since hooks modify the returned value.