<!--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=296837) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal via @mayra-cabrera [here](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46358#note_477825469) > It'd be great if we could split the tests on this file somehow, or perhaps create a dedicate spec file for `merge_request_actions.rb` (e.g `merge_request_actions_spec.rb`), since this file is getting quite large (over 2k lines!). The quick actions for merge requests have specs to interpret/parse the commands but don't actually have tests to make sure the commands worked. Ex: Does `/assign_reviewer` actually assign the reviewer to the MR? <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. -->