DC-3653: Integration tests for issue-view panel - #555
Merged
Conversation
mbeczek-atlassian
self-requested a review
July 7, 2026 14:01
mbeczek-atlassian
approved these changes
Jul 7, 2026
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.
Adds integration tests for the Slack panel in the issue view, following the pattern of the equivalent Confluence functional tests.
The goal is to prevent regressions like POSTSEFCON-10618 - a runtime dependency-injection failure that broke the panel but couldn't be caught by unit tests, since those mock the injected dependencies. The tests cover both directions: the panel data REST endpoint (inbound) and issue-event notifications to Slack (outbound).