Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3024

Polarion Improvements

XMLWordPrintable

    • Polarion Improvements
    • False
    • None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      This Epic represents improvements that are needed for OSSM QE Polarion test case and test run artifacts.
       

      References:
      1) From Brian Murray
      There is a wealth of information that can be found here:
      https://source.redhat.com/groups/public/polarion
       
      There you can find solutions and how-to's but, unfortunately, it does not include a very good best practices model.
      Please look around there.  After some discussions we agree to follow the same pattern that is do it by ACM team in releases, more information about the agreement about releases and displayed information here: https://docs.google.com/document/d/1vcfekYfUDA3gUoiNU5qE7kCmxVgLdb-CvLhV-JVoBZk/edit
       

      • In general always do the following
      • Link all test cases to at least one requirement using the verified link
      • Add requirements to plans (releases) when possible or desired
      • Create test run templates whenever possible.  Take advantage of queries to get the test cases you want in the test runs
      • Always set the planned in field in test runs so that all test runs can be linked to a release (plan)

      If you follow these basic steps you will ensure traceability between requirements, test cases, and plans.
       
      2) From Wei Sun from OpenShift
      https://source.redhat.com/groups/public/polarion/polarion_wiki/best_practices_for_polarion_admins#jive_content_id_Add_Custom_Fields_460546
       
      3) From Polarion
      https://docs.plm.automation.siemens.com/content/polarion/19.3/help/en_US/user_and_administration_help/user_guide/polarion_for_project_managers/dashboards_and_reports/overview_of_dashboards_and_reports.html

      For more information about the definition of the Test Run custom fields and discussion in meetings you may need to go tho this documents:

       

       

            frherrer@redhat.com Francisco Herrera Lira
            mmahoney@redhat.com Matthew Mahoney
            Filip Brychta, Francisco Herrera Lira, Matthew Mahoney
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: