Skip to content

Refactor the pipeline feature spec

What does this MR do?

In the spec/features/projects/pipelines/pipeline_spec.rb we visit the pipeline page in the before block. Causing in the ETag middleware without a status.

When visiting the page again after creating a status, the page would not be re-rendered. This makes sure we only access the page once per spec.

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59747

Does this MR meet the acceptance criteria?

Edited by Bob Van Landuyt

Merge request reports