davinci_pdex_test_kit 0.9.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 53ae12fc4c0ce1813450d5b139c04b489cc9d7a8a5db03002b0cecf683986b83
+  data.tar.gz: 03fdbb64fa1da8eb461087db829f9965e4a60a582aa285ce08835ffbe0151f5c
+SHA512:
+  metadata.gz: c435c9cf7ef61a2b12122a7c3dc1f75c2cd9c6c2e703ec572e5bba161232f529d4338538e4b5dfc93fcb095ed99b81d6ef9f2f8c6a2e8eb8371af58a7632b012
+  data.tar.gz: 2ee7697f2c9e875ce880282fe1c6da4d4e34028c3113bba0c16e4053d8d846d1d0d2b2844681231580814ad1296dd7315ec671f50ab2d1649d9ef1272da320a1

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/lib/davinci_pdex_test_kit/docs/payer_client_suite_description_v200.md

@@ -0,0 +1,91 @@
+The Da Vinci PDex Test Kit Payer Client Suite validates the conformance of payer client
+systems to the STU 2 version of the HL7® FHIR®
+[Da Vinci Payer Data Exchange (PDex) Implementation Guide](https://hl7.org/fhir/us/davinci-pdex/STU2/).
+
+## Scope
+
+These tests are a **DRAFT** intended to allow payer implementers to perform
+preliminary checks of their systems against PDex IG requirements and [provide
+feedback](https://github.com/inferno-framework/davinci-pdex-test-kit/issues)
+on the tests. Future versions of these tests may validate other
+requirements and may change the test validation logic.
+
+## Test Methodology
+
+Inferno will simulate a PDex payer server for the client under test to interact with. The 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 PDex requirements around
+[single member payer-to-payer data exchange](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html)
+the transfer of member data from an old payer (represented by Infero) to a new payer
+(represented by the client under test). This includes
+- The ability of the client to complete the payer to payer data exchange workflow by
+    - Initiating the request by invoking the `$member-match` operation.
+    - Fetching all clinical data available from the old payer (Inferno) on the returned member.
+
+Because the process by which 
+[payer servers identify each other and establish trust](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#mtls-endpoint-discovery)
+is [still under active development](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#future-direction-for-discovery-and-registration),
+Inferno does not currently facilitate or validate this part of the workflow. 
+See the *Quick Start* section below for the specifics of how this test suite approaches authentication.
+
+For further details on limitations of these tests, see the *Testing Limitations* section below.
+
+All requests made by the client will be checked for conformance to the PDex
+IG requirements individually and used in aggregate to determine whether
+required features and functionality are present. HL7® FHIR® resources are
+validated with the Java validator using `tx.fhir.org` as the terminology server.
+
+## Running the Tests
+
+### Quick Start
+
+For Inferno to simulate a server that returns a matching patient and responds to requests
+for that patient's data using FHIR read and search APIs, Inferno only needs to be able to
+identify when requests come from the client under test. Inferno piggybacks on the request 
+authentication for this purpose. Testers must provide a bearer access token that will be 
+provided within the `Authentication` header (`Bearer <token>`) on all requests made to 
+Inferno endpoints during the test. Inferno uses this information to associate the message
+with the test session and determine how to respond. How the token provided to Inferno is 
+generated is up to the tester. 
+
+Note: authentication options for these tests have not been finalized and are subject to change
+as the requirements in the PDex IG evolve. If the implemented approach prevents you from using
+these tests, please 
+[provide feedback](https://github.com/inferno-framework/davinci-pdex-test-kit/issues) so the
+limitations can be addressed.
+
+### Postman-based Demo
+
+If you do not have a PDex client but would like to try the tests out, you can use
+[this postman collection](https://github.com/inferno-framework/davinci-pdex-test-kit/blob/main/PDEX.postman_collection.json)
+to make requests against Inferno for these tests. To use the Postman demo on this test session
+
+1. Download the [collection](https://github.com/inferno-framework/davinci-pdex-test-kit/blob/main/PDEX.postman_collection.json) and import it into [Postman](https://www.postman.com/downloads/).
+2. Select the `PDex Payer Client Postman Demo` from the preset dropdown in the upper left.
+3. Click `Run All Tests` button in the upper right and click the `Submit` button in the dialog
+  that appears.
+4. When a `User Action Required` dialog will appear requesting a `$member-match` request be made, 
+   use Postman to send the `$member-match` request found in the `$member-match Requests` folder.
+5. When a new `User Action Required` dialog will appear requesting clinical data requests be made,
+   use Postman to send some or all of the requests in the `Clinical Data Requests` folder and click
+   on the link in the dialog when done. If not all the requests are made, the test will not pass 
+   because the test requires that all available data be accessed.
+6. When a third `User Action Required` requesting additional `$member-match` requests be made
+   demonstrating coverage of all must support elements on `$member-match` submissions, use Postman to send any or all of the requests found in the `$member-match Requests` folder. If only the 
+   `$member-match missing CoverageToMatch` is sent, then the test will fail due to missing examples.
+
+The tests will complete and the results made available for review.
+
+## Testing Limitations
+
+The PDex IG is under active development and the IG authors intend to change the approach to the
+workflows included within future versions of the IG. In particular the payer to payer workflow
+will move from a single-patient workflow to a multi-patient workflow. This test suite focuses on
+validating the high-level payer to payer workflow and the ability of clients to use the current
+specification to access member data, without doing detailed validation of the mechanisms, 
+including authentication and trust establishment, because those details are likely to change 
+in future versions of the PDex specification.
+
+At this time, coverage of additional scenarios beyond the happy path payer to payer workflow
+are not validated. These scenarios will be tested in future versions of the tests.

data/lib/davinci_pdex_test_kit/docs/payer_server_suite_description_v200.md

@@ -0,0 +1,119 @@
+The Da Vinci PDex Test Kit Payer Server Suite validates the conformance of payer server
+systems to the STU 2 version of the HL7® FHIR®
+[Da Vinci Payer Data Exchange (PDex) Implementation Guide](https://hl7.org/fhir/us/davinci-pdex/STU2/).
+
+## Scope
+
+These tests are a **DRAFT** intended to allow payer implementers to perform
+preliminary checks of their systems against PDex IG requirements and [provide
+feedback](https://github.com/inferno-framework/davinci-pdex-test-kit/issues)
+on the tests. Future versions of these tests may validate other
+requirements and may change the test validation logic.
+
+## Test Methodology
+
+Inferno will simulate a PDex payer client for the server under test to interact with. The server
+will be expected to respond to requests made by Inferno. Over the course of these interactions,
+Inferno will seek to observe conformant handling of PDex requirements around
+[single member payer-to-payer data exchange](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html)
+the transfer of member data from an old payer (represented by the server under test) to a new payer
+(represented by Inferno). This includes
+- The ability of the server to complete the payer to payer data exchange workflow by
+    - Responding successfully to invocations of the `$member-match` operation.
+    - Returning requested clinical data for the matched member.
+- The ability of the server to handle the full scope of the PDex IG, such as
+    - Support PDex and US Core 3.1.1 search and read APIs, profile, and must support requirements
+    - Produce failure responses to `$member-match` requests
+
+Because the process by which 
+[payer servers identify each other and establish trust](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#mtls-endpoint-discovery)
+is [still under active development](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#future-direction-for-discovery-and-registration),
+Inferno does not currently facilitate or validate this part of the workflow. 
+See the *Authentication* section below for the specifics of how this test suite approaches authentication.
+
+Note additionally that because the member matching logic is not specified within the implementation
+guide and Inferno will not know ahead of time the contents of server under test, testers are required
+to provide request bodies for `$member-match` invocations that they know will return the outcome
+expected by the test. Inferno will validate that these request bodies conform to the [`$member-match`
+input parameter requirements](https://hl7.org/fhir/us/davinci-hrex/StructureDefinition-hrex-parameters-member-match-in.html).
+
+For further details on limitations of these tests, see the *Testing Limitations* section below.
+
+All tester-provided requests and responses returned by the server will be checked 
+for conformance to the PDex IG requirements individually and used in aggregate to determine whether
+required features and functionality are present. HL7® FHIR® resources are
+validated with the Java validator using `tx.fhir.org` as the terminology server.
+
+## Running the Tests
+
+### Quick Start
+
+Execution of these tests require a significant amount of tester input in the
+form of requests that Inferno will make against the server under test.
+
+If you would like to try out the tests using examples from the IG against the
+[PDex reference server hosted on FHIR Foundry](https://pdex-server.davinci.hl7.org/fhir), you can do so by 
+1. Selecting the *PDex Payer Server Preset for FHIR Foundry RI* option from the Preset dropdown in the upper left
+2. Clicking the *Run All Tests* button in the upper right
+3. Clicking the *Submit* button at the bottom of the input dialog
+
+Note that the reference implementation is not expected to pass the tests at this time.
+
+You can run these tests using your own server by updating the "FHIR Server Endpoint URL" and 
+"OAuth Credentials" inputs. Additional inputs to update to values specific to your implementation 
+include:
+- "Member Match Request for one match"
+- "Member Match Request for no matches"
+- "Member Match Request for multiple matches"
+- "Patient IDs"
+
+Details on these inputs can be found below.
+
+## Test Configuration Details
+
+The details provided here supplement the documentation of individual fields in the input dialog
+that appears when initiating a test run.
+
+### Server identification
+
+Requests will be made to the `/Patient/$member-match` and clinical data access endpoints under 
+the url provided in the "FHIR Server Endpoint URL" field.
+
+### Authentication
+
+The PDex payer to payer workflow contains a
+[detailed approach to endpoint discovery](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#mtls-endpoint-discovery),
+[trust](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#trust-framework), and
+[scoped data access](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#data-retrieval-methods).
+However, the IG also states that significant parts of the IGs that are [expected to change](https://hl7.org/fhir/us/davinci-pdex/STU2/payertopayerexchange.html#future-direction-for-discovery-and-registration).
+Therefore, the tests currently assume that the server under test can provide a bearer token that Inferno
+will submit with all requests. If this simplified approach prevents you from using these tests, please 
+[provide feedback](https://github.com/inferno-framework/davinci-pdex-test-kit/issues) so the
+limitations can be addressed.
+
+### $member-match Request Bodies
+
+Three inputs for the test suite ask the tester to provide bodies for `$member-match` submissions:
+- "Member Match Request for one match"
+- "Member Match Request for no matches"
+- "Member Match Request for multiple matches"
+
+In each case, provide the raw json for the body that Inferno will use to invoke the server's
+`$member-match` operation that will elicit an appropriate response.
+
+### Complete Patients
+
+Inferno will test that the server's FHIR API allows for access to all clinical data covered by
+the PDex IG and the US Core IG that it inherits from. In order to do so, it needs the id of 
+one or more patients in the "Patient IDs" input. It will use the patient id or ids provided
+to fetch clinical data and check that the required profiles and must support elements are represented.
+
+## Testing Limitations
+
+The PDex IG is under active development and the IG authors intend to change the approach to the
+workflows included within future versions of the IG. In particular the payer to payer workflow
+will move from a single-patient workflow to a multi-patient workflow. This test suite focuses on
+validating the high-level payer to payer workflow and the ability of servers to use the current
+specification to make member data available, without doing detailed validation of the mechanisms, 
+including authentication and trust establishment, because those details are likely to change 
+in future versions of the PDex specification.

data/lib/davinci_pdex_test_kit/ext/inferno_core/record_response_route.rb

@@ -0,0 +1,98 @@
+require 'hanami/controller'
+
+module Inferno
+  module DSL
+    # A base class for creating routes with custom response logic. Requests and responses are tagged and saved.
+    # @private
+    # @see Inferno::DSL::Runnable#resume_test_route
+    class RecordResponseRoute < Hanami::Action
+      include Import[
+                requests_repo: 'inferno.repositories.requests',
+                results_repo: 'inferno.repositories.results',
+                test_runs_repo: 'inferno.repositories.test_runs',
+                tests_repo: 'inferno.repositories.tests'
+              ]
+
+      def self.call(...)
+        new.call(...)
+      end
+
+      # @private
+      def test_run_identifier_block
+        self.class.singleton_class.instance_variable_get(:@test_run_identifier_block)
+      end
+
+      # @private
+      def build_response_block
+        self.class.singleton_class.instance_variable_get(:@build_response_block)
+      end
+
+      # @private
+      def tags
+        self.class.singleton_class.instance_variable_get(:@tags)
+      end
+
+      # @private
+      def resumes?(test)
+        instance_exec(test, &self.class.singleton_class.instance_variable_get(:@resumes))
+      end
+
+      # @private
+      def find_test_run(test_run_identifier)
+        test_runs_repo.find_latest_waiting_by_identifier(test_run_identifier)
+      end
+
+      # @private
+      def find_waiting_result(test_run)
+        results_repo.find_waiting_result(test_run_id: test_run.id)
+      end
+
+      # @private
+      def update_result(waiting_result)
+        results_repo.update_result(waiting_result.id, 'pass')
+      end
+
+      # @private
+      def persist_request(request, test_run, waiting_result, test)
+        requests_repo.create(
+          request.to_hash.merge(
+            test_session_id: test_run.test_session_id,
+            result_id: waiting_result.id,
+            name: test.config.request_name(test.incoming_request_name),
+            tags:
+          )
+        )
+      end
+
+      # @private
+      def find_test(waiting_result)
+        tests_repo.find(waiting_result.test_id)
+      end
+
+      # @private
+      def handle(req, res)
+        request = Inferno::Entities::Request.from_hanami_request(req)
+
+        test_run_identifier = instance_exec(request, &test_run_identifier_block)
+
+        test_run = find_test_run(test_run_identifier)
+
+        halt 500, "Unable to find test run with identifier '#{test_run_identifier}'." if test_run.nil?
+
+        waiting_result = find_waiting_result(test_run)
+        test = find_test(waiting_result)
+
+        test_runs_repo.mark_as_no_longer_waiting(test_run.id) if resumes? test
+
+        update_result(waiting_result) if resumes? test
+
+        instance_exec(request, test, waiting_result, &build_response_block)
+
+        Inferno::Entities::Request.to_hanami_response(request, res)
+        persist_request(request, test_run, waiting_result, test)
+
+        Jobs.perform(Jobs::ResumeTestRun, test_run.id) if resumes? test
+      end
+    end
+  end
+end

data/lib/davinci_pdex_test_kit/ext/inferno_core/request.rb

@@ -0,0 +1,19 @@
+module Inferno
+  module Entities
+    class Request
+      def self.to_hanami_response(request, response)
+        response.status = request.status
+        response.body = request.response_body
+        request.response_headers.each do |header|
+          response.headers[header.name] = header.value
+        end
+
+        response
+      end
+
+      def response_headers=(headers_hash)
+        headers.concat(headers_hash.map { |key, value| Header.new(name: key.to_s, value:, type: 'response') })
+      end
+    end
+  end
+end

data/lib/davinci_pdex_test_kit/ext/inferno_core/runnable.rb

@@ -0,0 +1,18 @@
+require_relative 'record_response_route'
+
+module Inferno
+  module DSL
+    module Runnable
+      def record_response_route(method, path, tags, build_response, resumes: ->(_) { true }, &block)
+        route_class = Class.new(Inferno::DSL::RecordResponseRoute) do |klass|
+          klass.singleton_class.instance_variable_set(:@build_response_block, build_response)
+          klass.singleton_class.instance_variable_set(:@test_run_identifier_block, block)
+          klass.singleton_class.instance_variable_set(:@tags, Array.wrap(tags))
+          klass.singleton_class.instance_variable_set(:@resumes, resumes)
+        end
+
+        route(method, path, route_class)
+      end
+    end
+  end
+end