Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-6889 Implement phase 1 of recording compliance events for long-term storage
  3. ACM-6890

[QE] ACM-6889: Implement phase 1 of recording compliance events for long-term storage

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • GRC, QE
    • False
    • None
    • False
    • ACM-2047 - ACM Store Compliance History
    • GRC Sprint 2024-01, GRC Sprint 2024-02, GRC Sprint 2024-05

      Completion checklist:

      If Analysis/overview was done and no QE effort is required: Sub-Task can be Closed.

      [X] - Test cases created in Polarion and referenced here
      [X] - Test cases are reviewed and approved
      [X] - Test runs executed in Polarion and referenced here

       

      Test run: https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/testrun?id=GRC-Test-ACM-6889 

      Pre-reqs setup is described in https://issues.redhat.com/browse/ACM-9649  

      Test scenarios:

       

      Scenarios Expected
      result
      Polarion test case Manual | Automate
      1. Verify compliance history record in DB with a compliant config policy for all managed clusters at “Ready” state Successful query of records per cluster name and policy name after compliance https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43763 To be automated
      2. Verify compliance history record in DB with a non-compliant config policy for all managed clusters at “Ready” state Successful query of records per cluster name and policy name after non-compliance https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43763 To be automated
      3. Generate a CSV file report for a policy for all managed clusters Successful generation of CSV file which contains all histories for all managed clusters https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43764 To be automated
      4. Query compliance history of a policy for a managed cluster by event.compliance and cluster.name Successful query of records per cluster.name and event.compliance https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43765 To be automated
      5. Query compliance history of a policy for a managed cluster by ?sort=policy.namespace,policy.name and cluster.name Successful query of records per policy.namespace,policy.name and cluster.name with sorting done on policy.namespace  https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43765 To be automated
      6. User with “get” access of open-cluster-management:managedcluster:local-cluster to only local-cluster can query only the compliance history of the local-cluster Running as a custom user, successful query of records per cluster.name and policy.name for the local-cluster only https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43766 To be automated
      7. User with “get” access of open-cluster-management:managedcluster:cluster-1 to only cluster-1 can only query the compliance history of the cluster-1 Running as a custom user, successful query of records per cluster.name and policy.name for the cluster-1 only https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43767 To be automated
      8. Verify connection error event is reported when secret governance-policy-database contains invalid DB info The event will be sent into secret’s namespace https://polarion.engineering.redhat.com/polarion/#/project/RHACM4K/workitem?id=RHACM4K-43768 To be automated

       

       

              drkho Derek Ho
              acm-jira-bot ACM Bot
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: