Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-909

externalize cypress command-timeout config' for CI

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      currently, on cypress, we use the same test-run expiration value for CI runs as for local development.
      this is done in cypress.config.js, via the defaultCommandTimeout option.

      as developer machines are not bound by the same restrictions as CI instances (e.g. dev machines are often more resourceful, I/O is trivial as local/remote test servers reside on the same machine, etc.), they allow for shorter timeouts.

      to utilize that, we should externalize the setting of this option to allow CI pipelines independent control (e.g. via an env-var override), and have a short default value in cypress.config.js for use during development.

      for context, see this thread from the MR which introduced the initial cypress-framework impl'.

              Unassigned Unassigned
              emalka@redhat.com Eliran Malka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: