Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43906

Creation tests for "Git" flow

XMLWordPrintable

    • Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3

      Covering Git (with credentials) is required to make the ATH coverage complete. 

      Requirements https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit

      Scope

      Ideally we'd test all of the below scenarios:

       

      Priority SCM Repo Type Clone URL Credentials? Jenkinsfile? Success? Details
      1 BitBucket Public HTTPS "Default" Yes Yes Activity w/ builds
      1 BitBucket Public HTTPS "Default" No Yes Activity "No Jenkinsfile"
      4 BitBucket Private HTTPS "Default" Yes No "Invalid Credential"
      3 BitBucket Private HTTPS Invalid user / pass Yes No "Invalid Credential"
      2 BitBucket Private HTTPS Valid user / pass Yes Yes  
      4 BitBucket Public SSH "Default" Yes No? I believe SSH always requires a valid key whether it's public or private?
      3 BitBucket Private SSH Invalid private key Yes No "Invalid Credential"
      2 BitBucket Private SSH Valid private key Yes Yes  

          [JENKINS-43906] Creation tests for "Git" flow

          Cliff Meyers added a comment -

          michaelneale I took a stab at the scenarios for Git. This list might be unrealistic. Perhaps we should add a "Priority" column and call out the most important tests to start with? Probably SSH valid / invalid, HTTPS private valid / invalid, then HTTPS public w/ and w/o Jenkinsfile?

          Cliff Meyers added a comment - michaelneale  I took a stab at the scenarios for Git. This list might be unrealistic. Perhaps we should add a "Priority" column and call out the most important tests to start with? Probably SSH valid / invalid, HTTPS private valid / invalid, then HTTPS public w/ and w/o Jenkinsfile?

          Cliff Meyers added a comment -

          I suggest using Bitbucket just because it's a different provider for us to test with, and at least a few of the bug reports in the field for Git involved people using Bitbucket. We could probably create a dedicated test user with three repos (public w/ JF, public w/o JF, private w/ JF) to account for all the scenarios.

          Cliff Meyers added a comment - I suggest using Bitbucket just because it's a different provider for us to test with, and at least a few of the bug reports in the field for Git involved people using Bitbucket. We could probably create a dedicated test user with three repos (public w/ JF, public w/o JF, private w/ JF) to account for all the scenarios.

          Michael Neale added a comment -

          cliffmeyers yes priority would be good. I was thinking to start with - the simplest end-to-end thing to know it works at all would be a very good start before diving into permutations.

          Michael Neale added a comment - cliffmeyers yes priority would be good. I was thinking to start with - the simplest end-to-end thing to know it works at all would be a very good start before diving into permutations.

          Cliff Meyers added a comment -

          Took a stab to indicate simplest possible use cases first, then those w/ credentials, then error scenarios.

          Cliff Meyers added a comment - Took a stab to indicate simplest possible use cases first, then those w/ credentials, then error scenarios.

            imeredith Ivan Meredith
            cliffmeyers Cliff Meyers
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: