FHIR Chat · TestScript for failing scripts · implementers

Stream: implementers

Topic: TestScript for failing scripts


view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:49):

@Richard Ettema I'm tryng to understand http://hl7.org/fhir/testing.html#create

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:49):

<action>
  <assert>
    <response value="created"></response>
  </assert>
</action>

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:49):

the response implicitly refers to the response for the last operation, yes?

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:50):

I can't see that actually stated anywhere?

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:50):

... or is it linked to operation.responseId somehow?

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:53):

why isn't there a response codes for 500 errors?

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:53):

I don't see what the point of having response and responseCode is if their granularity is the same?

view this post on Zulip Grahame Grieve (Feb 07 2019 at 03:54):

we should have grouping codes at least (or only)

view this post on Zulip Richard Ettema (Feb 07 2019 at 16:28):

the response implicitly refers to the response for the last operation, yes?

Yes.

I can't see that actually stated anywhere?

The assert comments states "In order to evaluate an assertion, the request, response, and results of the most recently executed operation must always be maintained by the test engine." -- http://hl7.org/fhir/testscript-definitions.html#TestScript.setup.action.assert

why isn't there a response codes for 500 errors?

During the initial development of the TestScript resource, the response codes from the FHIR specification's RESTful API were chosen for inclusion in the coded values. The 5xx errors were not deemed specific enought for inclusion.

I don't see what the point of having response and responseCode is if their granularity is the same?
we should have grouping codes at least (or only)

Agreed. Based on my experience, I now generally prefer to use the responseCode element as it provides finer control over testing for one or more possible values for a given operation.

view this post on Zulip Grahame Grieve (Feb 08 2019 at 04:48):

ok, firstly, can we include some of the text your quoted in the definitions of the request, response related elements?

view this post on Zulip Grahame Grieve (Feb 08 2019 at 04:49):

and then, can we have 5xx codes added - at least 500. And I see the need for some grouping thing - success or failure, without having decide which code it was?


Last updated: Apr 12 2022 at 19:14 UTC