Skip to content

Add Feature specs to release CI component to Catalog and others

What does this MR do and why?

This MR adds new Feature specs to the CI/CD Catalog as we approach Beta. For more details on all of the specs that we needed to add, see the linked issue.

The general thinking here:

  1. We split out Feature specs in 4 files: the index page, details, settings and releases. I think this make a lot of sense because they each test very different aspects of the Catalog.
  2. Releases and Settings have small overlaps, but overall I think we need both. Releases mock the catalog resources and go through to make real releases through the UI so we are making sure that users can release projects that are resources to the Catalog. Settings is about showing and hiding resources when toggling on and off, but we make sure that this can be done with or without releases.

Screenshots or screen recordings

No change

How to set up and validate locally

Green pipeline

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #432824

Edited by Frédéric Caplette

Merge request reports