pub struct TestScriptSetupActionBuilder { /* private fields */ }Expand description
Builder for TestScriptSetupAction.
Implementations§
Source§impl TestScriptSetupActionBuilder
impl TestScriptSetupActionBuilder
Sourcepub fn id(self, value: String) -> TestScriptSetupActionBuilder
pub fn id(self, value: String) -> TestScriptSetupActionBuilder
Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Sourcepub fn extension(self, value: Vec<Extension>) -> TestScriptSetupActionBuilder
pub fn extension(self, value: Vec<Extension>) -> TestScriptSetupActionBuilder
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Sourcepub fn modifier_extension(
self,
value: Vec<Extension>,
) -> TestScriptSetupActionBuilder
pub fn modifier_extension( self, value: Vec<Extension>, ) -> TestScriptSetupActionBuilder
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Sourcepub fn operation(
self,
value: TestScriptSetupActionOperation,
) -> TestScriptSetupActionBuilder
pub fn operation( self, value: TestScriptSetupActionOperation, ) -> TestScriptSetupActionBuilder
The setup operation to perform
The operation to perform.
Sourcepub fn operation_ext(
self,
value: FieldExtension,
) -> TestScriptSetupActionBuilder
pub fn operation_ext( self, value: FieldExtension, ) -> TestScriptSetupActionBuilder
Extension field.
Sourcepub fn assert(
self,
value: TestScriptSetupActionAssert,
) -> TestScriptSetupActionBuilder
pub fn assert( self, value: TestScriptSetupActionAssert, ) -> TestScriptSetupActionBuilder
The assertion to perform
Evaluates the results of previous operations to determine if the server under test behaves appropriately.
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.
Sourcepub fn assert_ext(self, value: FieldExtension) -> TestScriptSetupActionBuilder
pub fn assert_ext(self, value: FieldExtension) -> TestScriptSetupActionBuilder
Extension field.