Repository navigation
test: cover queue scope, Zammad actors, mobile navigation and cache shutdown - #2
Merged
stefan-ernst merged 1 commit intoOct 2, 2026
Conversation
This was referenced Oct 2, 2026
Optic00
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I added regression tests for the companion Core fixes: workspace permission checks on collection queues, queue moves, concurrent writes and legacy global collections, Zammad completion after actor deactivation, and a stale mobile refresh returning 404.
I also restored the cache shutdown tests from Core PR #248 in the public suite, adapting the server fixture to the current session manager constructor. They check repeated and concurrent close, normal server shutdown and cleanup after failed startup.
The queue tests run against SQLite and PostgreSQL. The cache tests pass with the race detector. The mobile test renders the component and checks navigation behavior. Focused backend tests and the public quick suite passed against the companion Core branch.