Follow-up from "Implement new way to test ci process pipeline service"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The following discussion from !29405 (merged) should be addressed:

• @ayufan started a discussion: (+1 comment)

  TODO. I would love us in the future configure ref: and other parameters.

The general comment is that our pipeline testing should allow modeling all aspects of pipeline:

• running on a specific ref, like a tag or branch
• running on merge request
• defining changeset (and mocking it)
• defining worktree (and mocking it)
• defining commit message/title (and mocking it)

The intent is that by defining a starting conditions we could assert every type of creation of pipeline or pipeline processing in a generic format.