davinci_pas_test_kit 0.15.1 → 0.16.0

data/lib/davinci_pas_test_kit/client/user_input_response.rb

@@ -1,5 +1,11 @@
+require_relative '../cross_suite/response_selection_utils'
+
 module DaVinciPASTestKit
   module UserInputResponse
+    # Raised when a tester-provided response input is present but cannot be used. The
+    # message explains why in terms the tester can act on.
+    class InvalidInputError < StandardError; end
+
     def self.included(klass)
       klass.extend ClassMethods
     end
@@ -21,26 +27,42 @@ module DaVinciPASTestKit
 
     # Returns the tester-provided response candidates for the must support workflow
     # as a list of parsed JSON hashes. The input value may be a single entry or a
-    # JSON array of entries, where each entry is either a bare FHIR Bundle or a
-    # wrapper object holding the response Bundle under "bundle" alongside optional
-    # selection "criteria".
-    # Returns nil if the input is not present, not parseable, or malformed.
-    def self.response_candidates(result, operation)
+    # JSON array of entries, where each entry is either a bare FHIR Bundle or Parameters
+    # or a wrapper object holding the response resource under "bundle" alongside optional
+    # selection "criteria" - see ResponseSelectionUtils.
+    # Returns nil if the input has no value and raises InvalidInputError if the value
+    # is present but unusable. The configurable (the waiting test) supplies the input
+    # title so that the error names the input as the tester sees it.
+    def self.response_candidates(configurable, operation, result)
       input_name = operation == 'submit' ? 'ms_submit_responses' : 'ms_inquire_responses'
-      input_value = JSON.parse(result.input_json)&.find { |i| i['name'] == input_name }&.dig('value')
+      input_value = read_input(result, input_name)
       return unless input_value.present?
 
       candidates = JSON.parse(input_value)
       candidates = [candidates] unless candidates.is_a?(Array)
-      candidates if candidates.all? { |candidate| valid_candidate?(candidate) }
+      invalid_index = candidates.index { |candidate| !valid_candidate?(candidate) }
+      if invalid_index.present?
+        raise InvalidInputError,
+              "Entry #{invalid_index + 1} of the '#{input_title(configurable, input_name)}' input is not " \
+              'a FHIR Bundle or Parameters resource, or a wrapper object with one in the "bundle" key.'
+      end
+
+      candidates
     rescue JSON::ParserError
-      nil
+      raise InvalidInputError, "The '#{input_title(configurable, input_name)}' input is not valid JSON."
+    end
+
+    # Title of an input as shown to the tester in the Inferno UI, falling back to its name
+    def self.input_title(configurable, input_key)
+      input = configurable.config.inputs[input_key.to_sym]
+      (input&.title || input&.name || input_key).to_s
     end
 
     def self.valid_candidate?(candidate)
       return false unless candidate.is_a?(Hash)
 
-      candidate['resourceType'] == 'Bundle' || candidate['bundle'].is_a?(Hash)
+      ResponseSelectionUtils::RESPONSE_RESOURCE_TYPES.include?(candidate['resourceType']) ||
+        candidate[ResponseSelectionUtils::BUNDLE_KEY].is_a?(Hash)
     end
 
     def user_inputted_response?(input_key)
@@ -48,7 +70,25 @@ module DaVinciPASTestKit
     end
 
     def input_title(input_key)
-      config.inputs[input_key]&.title || config.inputs[input_key]&.name
+      UserInputResponse.input_title(self, input_key)
+    end
+
+    def response_description_for_wait(user_input, user_input_title, operation)
+      if user_input
+        <<~DESCRIPTION.strip
+          Inferno will respond to `#{operation}` requests with the content provided in the
+          '**#{user_input_title}**' input, with `{{...}}` fhirpath expressions replaced with
+          their value when evaluated against the request and timestamps and resources references
+          updated to be current and consistent. See the ["Response Instantiation" section](https://github.com/inferno-framework/davinci-pas-test-kit/wiki/Controlling-Simulated-Responses#response-instantiation)
+          of the Da Vinci PAS Test Kit wiki for details on these updates.
+        DESCRIPTION
+      else
+        <<~DESCRIPTION.strip
+          Inferno will respond to `#{operation}` requests with a mocked response based on the request.
+          See the ["Mocked Responses" section](https://github.com/inferno-framework/davinci-pas-test-kit/wiki/Controlling-Simulated-Responses#mocked-responses)
+          of the Da Vinci PAS Test Kit wiki for details on the mocked response.
+        DESCRIPTION
+      end
     end
 
     module ClassMethods

data/lib/davinci_pas_test_kit/client/v2.0.1/client_suite.rb

@@ -1,11 +1,13 @@
 require 'subscriptions_test_kit'
 require 'udap_security_test_kit'
 require 'smart_app_launch_test_kit'
+require_relative '../../cross_suite/validator_configuration'
 require_relative '../../cross_suite/validator_suppressions'
 require_relative '../../cross_suite/tags'
 require_relative '../endpoints/claim_endpoint'
 require_relative '../endpoints/token_endpoint'
 require_relative '../endpoints/subscription_create_endpoint'
+require_relative '../endpoints/subscription_read_endpoint'
 require_relative '../endpoints/subscription_status_endpoint'
 require_relative '../pas_client_options'
 require_relative 'pas_client_workflows_group'
@@ -22,33 +24,33 @@ module DaVinciPASTestKit
       id :davinci_pas_client_suite_v201
       title 'Da Vinci PAS Client Suite v2.0.1'
       description %(
-        The Da Vinci PAS Test Kit Client Suite validates the conformance of client
-        systems to the STU 2 version of the HL7® FHIR®
+        The Da Vinci PAS Test Kit Client Suite validates the conformance of PAS clients
+        to the STU 2 version of the HL7® FHIR®
         [Da Vinci Prior Authorization Support Implementation Guide](https://hl7.org/fhir/us/davinci-pas/STU2/).
 
         These tests are a **DRAFT** intended to allow PAS client implementers to perform
-        preliminary checks of their clients against PAS IG requirements and [provide
+        preliminary checks of their PAS clients against PAS IG requirements and [provide
         feedback](https://github.com/inferno-framework/davinci-pas-test-kit/issues)
         on the tests. Future versions of these tests may validate other
         requirements and may change the test validation logic.
 
         The best place to get started is the [Client Testing
         Walkthrough](https://github.com/inferno-framework/davinci-pas-test-kit/wiki/Client-Instructions-v2.0.1),
-        which provides a step-by-step guide for running the tests against a client and provides
+        which provides a step-by-step guide for running the tests against a PAS client and provides
         an example client implemented in Postman.  Visit the [Client Testing
         Details](https://github.com/inferno-framework/davinci-pas-test-kit/wiki/Client-Details)
         documentation for information about technical implementation and known limitations of these tests.
 
-        In this test suite, Inferno simulates a PAS server for the client under test to
-        interact with. The client will be expected to initiate requests to the server
+        In this test suite, Inferno simulates a PAS server for the PAS client to
+        interact with. The PAS client will be expected to initiate requests to the server
         and demonstrate its ability to react to the returned responses. Over the course
         of these interactions, Inferno will seek to observe conformant handling of PAS
         requirements, including:
-        - The ability of the client to initiate a prior authorization submission and react to
+        - The ability of the PAS client to initiate a prior authorization submission and react to
             - The approval of the request
             - The denial of the request
             - The pending of the request and a subsequent notification that a final decision was made
-        - The ability of the client to provide data covering the full scope of required by PAS, including
+        - The ability of the PAS client to provide data covering the full scope of required by PAS, including
             - The ability to send prior auth requests and inquiries with all PAS
               profiles and all must support elements on those profiles
             - The ability to handle responses that contain all PAS profiles and all must support elements on those
@@ -93,16 +95,29 @@ module DaVinciPASTestKit
       )
 
       fhir_resource_validator do
-        igs 'hl7.fhir.us.davinci-pas#2.0.1'
+        igs(*V201_VALIDATOR_IGS)
 
         exclude_message do |message|
-          # Messages expected of the form `<ResourceType>: <FHIRPath>: <message>`
-          # We strip `<ResourceType>: <FHIRPath>: ` for the sake of matching
-          SUPPRESSED_MESSAGES.match?(message.message.sub(/\A\S+: \S+: /, ''))
+          V201_SUPPRESSED_MESSAGES.match?(message.message.sub(VALIDATOR_MESSAGE_LOCATION_PREFIX, ''))
         end
 
         validation_context do
-          snomedCT '731000124108'
+          snomedCT SNOMED_CT_US_EDITION
+        end
+      end
+
+      # Used to verify responses sent by Inferno, which may be tester-provided, to
+      # ensure they don't contain extensions not defined in the PAS IG or its dependencies.
+      fhir_resource_validator NO_CUSTOM_EXTENSIONS_VALIDATOR do
+        igs(*V201_VALIDATOR_IGS)
+
+        exclude_message do |message|
+          V201_SUPPRESSED_MESSAGES.match?(message.message.sub(VALIDATOR_MESSAGE_LOCATION_PREFIX, ''))
+        end
+
+        validation_context do
+          snomedCT SNOMED_CT_US_EDITION
+          extensions [] # no extensions not in the spec
         end
       end
 
@@ -140,8 +155,8 @@ module DaVinciPASTestKit
       suite_endpoint :post, SESSION_INQUIRE_PATH, ClaimEndpoint
       suite_endpoint :post, FHIR_SUBSCRIPTION_PATH, SubscriptionCreateEndpoint
       suite_endpoint :post, SESSION_FHIR_SUBSCRIPTION_PATH, SubscriptionCreateEndpoint
-      suite_endpoint :get, FHIR_SUBSCRIPTION_INSTANCE_PATH, SubscriptionsTestKit::SubscriptionReadEndpoint
-      suite_endpoint :get, SESSION_FHIR_SUBSCRIPTION_INSTANCE_PATH, SubscriptionsTestKit::SubscriptionReadEndpoint
+      suite_endpoint :get, FHIR_SUBSCRIPTION_INSTANCE_PATH, SubscriptionReadEndpoint
+      suite_endpoint :get, SESSION_FHIR_SUBSCRIPTION_INSTANCE_PATH, SubscriptionReadEndpoint
       suite_endpoint :post, FHIR_SUBSCRIPTION_INSTANCE_STATUS_PATH, SubscriptionStatusEndpoint
       suite_endpoint :post, SESSION_FHIR_SUBSCRIPTION_INSTANCE_STATUS_PATH, SubscriptionStatusEndpoint
       suite_endpoint :get, FHIR_SUBSCRIPTION_INSTANCE_STATUS_PATH, SubscriptionStatusEndpoint

data/lib/davinci_pas_test_kit/client/v2.0.1/must_support/pas_client_must_support_request_profiles_test.rb

@@ -18,7 +18,7 @@ module DaVinciPASTestKit
         * PAS Device Request
         * PAS Nutrition Order
 
-        System are allowed to support only the request profiles that fit their use cases. However,
+        PAS clients are allowed to support only the request profiles that fit their use cases. However,
         they must support at least one of them (because `Claim.item.extension:requestedService` is a
         must support element) and for any request profiles they support, they must be able to
         populate all of the defined must support elements.
@@ -27,7 +27,7 @@ module DaVinciPASTestKit
         profile listed above. Then for each profile observed, it checks for the presence of
         each must support element defined in that profile.
 
-        The test will look through the instances included in submissions made by the client
+        The test will look through the instances included in submissions made by the PAS client
         for the following must support elements:
 
         ### PAS Medication Request

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_approval_group.rb

@@ -8,10 +8,10 @@ module DaVinciPASTestKit
   module DaVinciPASV201
     class PASClientApprovalGroup < Inferno::TestGroup
       id :pas_client_v201_approval_group
-      title 'Approval Workflow'
+      title 'Approval Response'
       description %(
-        During these tests, the client will initiate a prior authorization
-        request and show it can respond appropriately to an 'approved' decision.
+        During these tests, the PAS client will initiate a prior authorization
+        request and show it can react appropriately to an 'approved' decision.
       )
       run_as_group
 
@@ -24,16 +24,17 @@ module DaVinciPASTestKit
       test from: :pas_client_v201_response_bundle_validation_test,
            config: { options: { workflow_tag: APPROVAL_WORKFLOW_TAG } }
       test from: :pas_client_v201_response_attest,
-           title: 'Check that the client registers the request as approved (Attestation)',
+           title: 'Check that the PAS client registers the request as approved',
            description: %(
-             This test provides the tester an opportunity to observe their client following
+             During this test, the tester will observe the PAS client following
              the receipt of the approved response and attest that users are able to determine
              that the response has been approved.
            ),
            config: { options: {
              workflow_tag: APPROVAL_WORKFLOW_TAG,
-             attest_message: "I attest that the client system displays the submitted claim as 'approved' meaning " \
-                             'that the user can proceed with ordering or providing the requested service.'
+             attest_message: 'I attest that the PAS client did not error when handling the `$submit` ' \
+                             "response and displays the submitted claim as 'approved' meaning that the " \
+                             'user can proceed with ordering or providing the requested service.'
            } }
     end
   end

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_auth_smart_group.rb

@@ -7,13 +7,13 @@ module DaVinciPASTestKit
       id :pas_client_v201_auth_smart
       title 'Review Authentication Interactions'
       description %(
-        During these tests, Inferno will verify that the client interacted with Inferno's
+        During these tests, Inferno will verify that the PAS client interacted with Inferno's
         simulated SMART authorization server in a conformant manner when requesting access tokens
-        and that the client under test was able to use provided access tokens to make PAS
+        and that the PAS client was able to use provided access tokens to make PAS
         requests.
 
-        Before running these tests, execute the tests for at least one "PAS workflows" sub-group
-        so that the client will request an access token and use it on a PAS request.
+        Before running these tests, execute the tests for at least one "PAS Scenarios" sub-group
+        so that the PAS client will request an access token and use it on a PAS request.
       )
       run_as_group
 

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_auth_udap_group.rb

@@ -7,13 +7,13 @@ module DaVinciPASTestKit
       id :pas_client_v201_auth_udap
       title 'Review UDAP Authentication Interactions'
       description %(
-        During these tests, Inferno will verify that the client interacted with Inferno's
+        During these tests, Inferno will verify that the PAS client interacted with Inferno's
         simulated UDAP authorization server in a conformant manner when requesting access tokens
-        and that the client under test was able to use provided access tokens to make PAS
+        and that the PAS client was able to use provided access tokens to make PAS
         requests.
 
-        Before running these tests, execute the tests for at least one "PAS workflows" sub-group
-        so that the client will request an access token and use it on a PAS request.
+        Before running these tests, execute the tests for at least one "PAS Scenarios" sub-group
+        so that the PAS client will request an access token and use it on a PAS request.
       )
       run_as_group
 

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_denial_group.rb

@@ -11,10 +11,10 @@ module DaVinciPASTestKit
       include UserInputResponse
 
       id :pas_client_v201_denial_group
-      title 'Denial Workflow'
+      title 'Denial Response'
       description %(
-        During these tests, the client will initiate a prior authorization
-        request and show it can respond appropriately to a 'denied' decision.
+        During these tests, the PAS client will initiate a prior authorization
+        request and show it can react appropriately to a 'denied' decision.
       )
       run_as_group
 
@@ -30,17 +30,18 @@ module DaVinciPASTestKit
       test from: :pas_client_v201_response_bundle_validation_test,
            config: { options: { workflow_tag: DENIAL_WORKFLOW_TAG } }
       test from: :pas_client_v201_response_attest,
-           title: 'Check that the client registers the request as denied (Attestation)',
+           title: 'Check that the PAS client registers the request as denied',
            description: %(
-             This test provides the tester an opportunity to observe their client following
+             During this test, the tester will observe the PAS client following
              the receipt of the denied response and attest that users are able to determine
              that the response has been denied.
            ),
            config: { options: {
              workflow_tag: DENIAL_WORKFLOW_TAG,
-             attest_message: "I attest that the client system displays the submitted claim as 'denied', meaning " \
+             attest_message: 'I attest that the PAS client did not error when handling the `$submit` ' \
+                             "response and displays the submitted claim as 'denied', meaning " \
                              'that the user cannot proceed with ordering or providing the requested service without ' \
-                             'making adjustments and submitting for further approval.'
+                             'making adjustments and submitting for further review.'
            } }
     end
   end

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_must_support_group.rb

@@ -7,6 +7,7 @@ require_relative 'workflows/pas_client_request_bundle_validation_test'
 require_relative 'workflows/pas_client_response_bundle_validation_test'
 require_relative 'workflows/pas_client_inquire_request_bundle_validation_test'
 require_relative 'workflows/pas_client_inquire_response_bundle_validation_test'
+require_relative '../client_input_descriptions'
 
 module DaVinciPASTestKit
   module DaVinciPASV201
@@ -14,54 +15,55 @@ module DaVinciPASTestKit
       id :pas_client_v201_must_support
       title 'Must Support Elements'
       run_as_group
-      description %(
-        During these tests, the client will show that it supports all PAS-defined profiles and the must support
-        elements defined in them. This includes
+      description DaVinciPASTestKit.must_support_group_description('v2.0.1', 'da-vinci-pas-v201')
 
-        - The ability to make prior authorization submission and inquiry requests that contain all
-          PAS-defined profiles and their must support elements.
-        - The ability to receive in responses to those requests all PAS-defined profiles and their
-          must support elements.
+      # The must support response inputs already belong to pas_client_v201_gather_must_support
+      # (the wait test below); declaring them here too, before the receive group is defined,
+      # propagates them onto the bundle validation tests in that group as well, so they can tell
+      # whether a tester-provided response was used - see
+      # PasClientResponseBundleValidationTest/PasClientInquireResponseBundleValidationTest
+      # #failed_entities_description.
+      input :ms_submit_responses, optional: true
+      input :ms_inquire_responses, optional: true
 
-        Clients under test will be asked to make additional requests to Inferno demonstrating coverage
-        of all must support items in the requests. Clients must also demonstrate that they can handle
-        all response must support elements. Because Inferno's mocked responses do not include all must
-        support elements, testers will need to provide responses that include examples of all must
-        support elements for Inferno to respond with.
-
-        Note that Inferno will consider requests made during the workflow group of tests, so only
-        profiles and must support elements not demonstrated during those tests need to be submitted
-        as a part of these.
-      )
+      input_order :ms_submit_responses,
+                  :ms_inquire_responses,
+                  :client_id,
+                  :session_url_path
 
       # Combined receive group - single wait test for both submit and inquire
       group do
         id :pas_client_v201_must_support_receive
-        title 'Demonstrate Must Support Coverage'
-        description %(
-          Submit $submit and $inquire requests demonstrating coverage of must support elements.
-          Optionally, provide response bundles for Inferno to use when responding. Inferno will
-          verify both the requests received and the responses provided.
-        )
+        title MUST_SUPPORT_RECEIVE_GROUP_TITLE
+        description MUST_SUPPORT_RECEIVE_GROUP_DESCRIPTION
         run_as_group
 
         test from: :pas_client_v201_gather_must_support
-      end
-
-      # $submit Bundle Conformance Validation
-      group do
-        title '$submit Bundle Conformance'
-        description %(
-          Verify that the $submit request bundles sent by the client are conformant
-          and that the $submit response bundles provided for Inferno to send back
-          are conformant.
-        )
-        run_as_group
+        test from: :pas_client_v201_response_attest,
+             id: :pas_client_v201_response_attest_ms_submit_inquire,
+             title: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_TITLE,
+             description: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_DESCRIPTION,
+             config: { options: {
+               workflow_tag: MUST_SUPPORT_WORKFLOW_TAG,
+               no_requests_ok: true,
+               multiple_requests_ok: true,
+               attest_message: MUST_SUPPORT_SUBMIT_INQUIRE_ATTEST_MESSAGE
+             } } do
+          verifies_requirements 'hl7.fhir.us.davinci-pas_2.0.1@41'
+        end
 
         test from: :pas_client_v201_request_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
         test from: :pas_client_v201_response_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
+        test from: :pas_client_v201_inquire_request_bundle_validation_test,
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
+        test from: :pas_client_v201_inquire_response_bundle_validation_test,
+             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG, no_requests_ok: true,
+                                  multiple_requests_ok: true } }
       end
 
       # $submit Request Must Support (fail when errors detected)
@@ -70,22 +72,6 @@ module DaVinciPASTestKit
       # $submit Response Must Support (skip when errors detected)
       group from: :pas_client_v201_submit_response_must_support
 
-      # $inquire Bundle Conformance Validation
-      group do
-        title '$inquire Bundle Conformance'
-        description %(
-          Verify that the $inquire request bundles sent by the client are conformant
-          and that the $inquire response bundles provided for Inferno to send back
-          are conformant.
-        )
-        run_as_group
-
-        test from: :pas_client_v201_inquire_request_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
-        test from: :pas_client_v201_inquire_response_bundle_validation_test,
-             config: { options: { workflow_tag: MUST_SUPPORT_WORKFLOW_TAG } }
-      end
-
       # $inquire Request Must Support (fail when errors detected)
       group from: :pas_client_v201_inquire_must_support
 

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_pended_group.rb

@@ -13,10 +13,10 @@ module DaVinciPASTestKit
       include UserInputResponse
 
       id :pas_client_v201_pended_group
-      title 'Pended Workflow'
+      title 'Pended Response'
       description %(
-        During these tests, the client will initiate a prior authorization
-        request and show it can respond appropriately to a 'pended' decision, including
+        During these tests, the PAS client will initiate a prior authorization
+        request and show it can react appropriately to a 'pended' decision, including
         waiting for a notification that an update has been made
         and making an inquiry request to retrieve the final result.
       )
@@ -31,15 +31,15 @@ module DaVinciPASTestKit
                   :session_url_path
 
       group do
-        title 'Perform the pended workflow'
+        title 'Perform the pended scenario'
         description %(
-          All interactions for the pended prior authorization request workflow
-          between Inferno and the client under test will be performed during this test
+          All interactions for the pended prior authorization request scenario
+          between Inferno and the PAS client will be performed during this group
           including
-          - A `$submit` request from the client to Inferno where Inferno returns a pended response.
+          - A `$submit` request from the PAS client to Inferno where Inferno returns a pended response.
           - A notification that the prior authorization decision has been finalized from Inferno
-            to the client under test.
-          - An `$inquire` request from the client to Inferno where Inferno returns an approved response.
+            to the PAS client.
+          - An `$inquire` request from the PAS client to Inferno where Inferno returns an approved response.
         )
 
         test from: :pas_client_v201_pended_submit_test
@@ -53,17 +53,19 @@ module DaVinciPASTestKit
         test from: :pas_client_v201_response_bundle_validation_test,
              config: { options: { workflow_tag: PENDED_WORKFLOW_TAG } }
         test from: :pas_client_v201_response_attest,
-             title: 'Check that the client registers the request as pended (Attestation)',
+             title: 'Check that the PAS client registers the request as pended',
              description: %(
-              This test provides the tester an opportunity to observe their client following
+              During this test, the tester will observe the PAS client following
               the receipt of the pended response and attest that users are able to determine
               that the response has been pended and a decision will be forthcoming.
              ),
              config: { options: {
                workflow_tag: PENDED_WORKFLOW_TAG,
-               attest_message: "I attest that following the receipt of the 'pended' response to the submitted " \
-                               'claim, the client system indicates to users that a final decision on request ' \
-                               'has not yet been made.'
+               operation_tag: SUBMIT_TAG,
+               multiple_requests_ok: true,
+               attest_message: "I attest that the PAS client did not error when handling the 'pended' " \
+                               'response to the submitted claim and that it indicated to users that a final decision ' \
+                               'on the request had not yet been made.'
              } }
       end
 
@@ -73,7 +75,7 @@ module DaVinciPASTestKit
         test from: :subscriptions_r4_client_notification_input_verification,
              title: 'Tester-provided event notification Bundle is conformant',
              description: %(
-               This test checks that the notification Bundle sent to the client, which will be either
+               This test checks that the notification Bundle sent to the PAS client, which will be either
                the tester-provided notification Bundle in the **Claim updated notification JSON** input
                or mocked by Inferno based on details in the Subscription and submitted Claim, is conformant
                to Subscription Backport IG requirements.
@@ -87,10 +89,10 @@ module DaVinciPASTestKit
         test from: :subscriptions_r4_client_notification_input_payload_verification,
              title: 'Tester-provided event notification Bundle matches the Subscription',
              description: %(
-               This test checks that the notification Bundle sent to the client, which will be either
+               This test checks that the notification Bundle sent to the PAS client, which will be either
                the tester-provided notification Bundle in the **Claim updated notification JSON** input
                or mocked by Inferno based on details in the Subscription and submitted Claim, matches the details
-               requested in the Subscription provided during the **2.1** "PAS Subscription Setup" tests.
+               requested in the Subscription provided during the "Subscription Setup" tests.
              ),
              simulation_verification: true,
              config: {
@@ -102,9 +104,9 @@ module DaVinciPASTestKit
         # and testers have to demonstrate and attest that their systems work, which will require some
         # correspondence.
         test from: :subscriptions_r4_client_event_notification_verification,
-             title: 'Client accepts the "claim updated" event notification',
+             title: 'PAS client accepts the "claim updated" event notification',
              description: %(
-               This test checks that the client responds appropriately to the event notification request.
+               This test checks that the PAS client responds appropriately to the event notification request.
              )
       end
 
@@ -116,15 +118,19 @@ module DaVinciPASTestKit
         test from: :pas_client_v201_inquire_response_bundle_validation_test,
              config: { options: { workflow_tag: PENDED_WORKFLOW_TAG } }
         test from: :pas_client_v201_response_attest,
-             title: 'Check that the client registers the request as approved (Attestation)',
+             title: 'Check that the PAS client registers the request as approved',
              description: %(
-              This test provides the tester an opportunity to observe their client following
+              During this test, the tester will observe the PAS client following
               the receipt of the inquiry response with a final decision and attest that users
               are able to determine that the response has been approved in full.
              ),
              config: { options: {
                workflow_tag: PENDED_WORKFLOW_TAG,
-               attest_message: "I attest that the client system displays the submitted claim as 'approved' meaning that the user can proceed with ordering or providing the requested service." # rubocop:disable Layout/LineLength
+               operation_tag: INQUIRE_TAG,
+               multiple_requests_ok: true,
+               attest_message: 'I attest that the PAS client did not error when handling the `$inquire` ' \
+                               "response and displays the submitted claim as 'approved' meaning that the " \
+                               'user can proceed with ordering or providing the requested service.'
              } }
       end
     end

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_registration_group.rb

@@ -12,8 +12,8 @@ module DaVinciPASTestKit
       id :pas_client_v201_registration
       title 'Client Registration'
       description %(
-        Register the client under test with Inferno's simulated PAS Server,
-        including configuration of the system under test to make requests against
+        Register the PAS client with Inferno's simulated PAS Server,
+        including configuration necessary to make requests against
         Inferno's simulated PAS endpoints and enable authentication and authorization of PAS requests.
       )
       run_as_group

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_subscription_setup_group.rb

@@ -8,8 +8,8 @@ module DaVinciPASTestKit
       id :pas_client_v201_subscription_setup
       title 'Subscription Setup'
       description %(
-        These tests verify that the client can create a Subscription instance
-        that will tell the Payer how to notify the client when pended claims
+        These tests verify that the PAS client can create a Subscription instance
+        that will tell the Payer how to notify the PAS client when pended claims
         are updated.
       )
       run_as_group

data/lib/davinci_pas_test_kit/client/v2.0.1/pas_client_workflows_group.rb

@@ -6,9 +6,9 @@ module DaVinciPASTestKit
   module DaVinciPASV201
     class PASClientWorkflowsGroup < Inferno::TestGroup
       id :pas_client_v201_workflows
-      title 'PAS Workflows'
+      title 'PAS Scenarios'
       description %(
-        The workflow tests verify that the client can participate in complete end-to-end prior
+        The scenario tests verify that the PAS client can participate in complete end-to-end prior
         authorization interactions, initiating requests and reacting appropriately to the
         responses returned.
       )