Follow-up from "Add Container Expiration Policy & Service Desk Setting to GitLab Migration"
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=347296) </details> <!--IssueSummary end--> The following discussion from !75653 should be addressed: - [ ] @brytannia started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/75653#note_753823399): (+1 comment) > question: I see that this is a repeating test case and it's logical because `ServiceDeskSettingPipeline` includes its behavior from `NdjsonPipeline`. It would be good to extract this test so we can reuse it to test similar behavior on different classes. What do you think, is it possible and does it make sense?
issue