Uploaded image for project: 'EJBCA'
  1. EJBCA
  2. ECA-8380

ACME: QA Testing of ACME Changes

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EJBCA 7.3.0, EJBCA 7.2.1
    • Fix Version/s: EJBCA 7.3.0
    • Component/s: CA GUI, Protocols
    • Labels:
      None
    • Environment:
      EJBCA: trunk, 7.2.1 and 7.3.0
      OS: CentOS or Ubuntu
      AppServer: Wildfly 14
      JDK: OpenJDK11
      Network Interface: IPv4 and IPv6
      Database: MariaDB
      Selenium: Firefox
    • Sprint:
      EJBCA Team Bob - 2019 w31, EJBCA Team Bob - 2019 w34, EJBCA Team Bob - 2019 w37

      Description

      tCreate both a test approach and test cases to support, Ideally automate it:

      1. Setup of:

      • Create CA and Cryptotoken
      • Create Certificate Profile
      • Create End Entity Profile

      For each ACME Client in (Certbot, PJAC, Acme Tiny)

      2. Regression Test using the available manual tests:

      • ECAQA-187
      • ECAQA-189
      • ECAQA-183
      • ECAQA-188
      • ECAQA-184
      • ECAQA-185

      3. Editing step 3. The ACME Blackbox test workflow should be:
      A. New HTTP ACME Alias, Non-default

      • Create an Acme Alias
      • Create a new HTTP configuration
      • Run ACME Client commands
      • Verify Audit Log
      • Verify Generated EEP
        *Website: http-example

      B. New DNS ACME Alias, Non-default

      • Create an ACME Alias
      • Create a new HTTP configuration
      • Run ACME Client commands
      • Verify Audit Log
      • Verify Generated EEP
      • DNS: dns.maggiesworld.se

      C. New ACME Alias, Default

      • Create an ACME Alias
      • Create a new HTTP configuration
      • Run ACME Client commands
      • Verify Audit Log
      • Verify Generated EEP

      *Website: default-example

      D. No Alias

      • Create a new HTTP configuration
      • Run ACME Client commands
      • Verify Audit Log

      *Website: http-noalias

      For each generated certificate, run isRevoked

      2. Jiras verified will be:

      NOTE: Make the assert certificate lifestyle realtime by:

      • isNewCertificateIssued
      • IsCertificateValid : Yes = Revoked ? No
      • IsCertificateRevoked: Yes = revoke again and assert error ? No

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              margarett Margaret Thomas
              Reporter:
              margarett Margaret Thomas
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: