Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2153

Adding support to include custom tests while triggering Jenkins Jobs.

    XMLWordPrintable

Details

    • Task
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • None
    • not-targeted
    • testing
    • None
    • 1

    Description

      Changes in components like backup, exporter, logging with no change in test framework necessitate quick run of component tests respectively with the new image.

      This at the moment can be achieved by specifying tests in Custom suite which in turn is generated through a gerrit review.

      Hence, It would be nice to have a field in our list of Jenkins params to specify the custom tests which we want to run while triggering the job rather than the cumbersome process to generate a custom suite to do so.

      Dev Env. has the functionality to specify the tests during run time, we need to replicate the same in QE setup.

      CC: Roo Thorp 

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          simon.murray Simon Murray added a comment -

          Just FYI, for 2.3 I plan to categorize tests based on feature e.g. TLS, persistent volumes, sync gateway so you can just subsets of tests based on the area of interest.  Would that be also helpful in this respect?  Imagine...

          test-operator --feature xdcr --feature tls

          simon.murray Simon Murray added a comment - Just FYI, for 2.3 I plan to categorize tests based on feature e.g. TLS, persistent volumes, sync gateway so you can just subsets of tests based on the area of interest.  Would that be also helpful in this respect?  Imagine... test-operator --feature xdcr --feature tls

          I think that would be the best approach to achieve the desired result. Similar to how we categorise our tests while declaring them: https://github.com/couchbase/couchbase-operator/blob/master/test/e2e/util_test.go#L356 Excellent plan!

          prateek.kumar Prateek Kumar added a comment - I think that would be the best approach to achieve the desired result. Similar to how we categorise our tests while declaring them: https://github.com/couchbase/couchbase-operator/blob/master/test/e2e/util_test.go#L356  Excellent plan!

          I guess this can be closed now?

          patrick.stephens Patrick Stephens (Inactive) added a comment - I guess this can be closed now?

          People

            prateek.kumar Prateek Kumar
            prateek.kumar Prateek Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty