Acceptance tests for nested project and funky branch name regressions

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      We need to cover some of the recent regressions involving jobs nested in folders or branch names that were not properly URI encoded.

      See the following issues:

      Other issues that would benefit from this:

      Possibly JENKINS-36618 too, although we do have a good unit test for that one.

      Plan to cover them:

      • Ensure that a top-level project and nested project are created with the same name; assert that pipelines view shows the correct number of items (JENKINS-36618).
      • Ensure a nested multi-branch project is added that has branches with non-standard names. Navigate to run detail for "funky branch name" via Branches tab (JENKINS-36616)
      • Ensure we can kick off a run for the above project (JENKINS-36615)
      • Ensure the logs render for the above project (JENKINS-36613)
      • Ensure the test results render for the above project (obviously, the project needs to actually render test results. JDL is a good candidate for this now) (JENKINS-36674)
      • Ensure navigating directly to a run for the above project then closing the modal navigates back to the activity screen (JENKINS-36619)

            Assignee:
            Thorsten Scherler
            Reporter:
            Cliff Meyers
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: