-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow using retest ID locator without GM #570
Comments
This has been partly addressed with #612, where it for now tries to find a retest ID, if no Golden Master has been created yet. This implementation is similar (if not equal) to the originally proposed solution and does no assumptions or semi-intelligent lookups. It simply queries the soon-to-be-persisted state for the retest ID instead of loading the previous one. Therefore it is the users responsibility to ensure that the retest ID is present. Since then, I have documented the generation in more detail, but we should document this specific feature with its effects more thoroughly before release (e.g. that the default implementation is in fact deterministic). Of course, the use cases are fairly limited, when not precisely knowing how the active I will keep this open, until the feature has been documented. However, feel free to create more issues regarding your other points. |
Problem
Using the retest ID as a locator is currently only possible if a GM exists. It would be helpful if it could also be used without a GM, which requires
RetestIdProvider
to be deterministic.Solution
@roesslerj proposed a draft via #563, but this still needs some work. Quote from my comment:
The text was updated successfully, but these errors were encountered: