Fix test interaction with smart albums #1428
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is another PR with cherry-picking from #1414 in order to keep #1414 lean.
The smart albums (
PublicAlbum
,RecentAlbum
,StarredAlbum
,PublicAlbum
) have been implemented as singletons in order to cache them incl. their photo relation etc. during the same HTTP request. This is fine for productive code.However, during testing all "requests" are part of the same test process and hence caching is a problem if we query the smart albums in the same test and expect different results. To this end the productive code has always been containing code which was only necessary for tests. (Yes, this has always been a bad design, but is was an easy work-around back then.)
While I have been working on #1414 I tumbled across more issues due this caching effect. Hence, it has been time to eventually fix this problem.
This PR does three things:
PublicAlbum
,RecentAlbum
,StarredAlbum
andPublicAlbum
InteractWithSmartAlbums
to the test code