mirror of
https://github.com/google/nomulus.git
synced 2025-06-29 07:43:37 +02:00
In testSuccess_expandSingleEvent_notIdempotentforDifferentRecurring(), two Recurring entities are created with the only difference being their IDs. If we don't order the Recurrings by ID when loading them there is no guarantee which one is expanded first. In this test the expected OneTime entities are created with the assumption that the first loaded DomainHistory (parent of a OneTime) corresponds to the expanding the Recurring with the smaller ID (2L). Since the DomainHistory entities are loaded in order of IDs, and the IDs are created monotonically in time in tests, we need to load the Recurrings in order of their IDs to ensure that the first DomainHistory is the result of expanding the Recurring with ID of 2L. This should impose minimum performance penalty as we are ordering by the primary key. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/google/nomulus/1204) <!-- Reviewable:end --> |
||
---|---|---|
.. | ||
gradle/dependency-locks | ||
src | ||
WEB-INF/appengine-generated | ||
build.gradle | ||
Dockerfile |