Struct TestPlanTestCase

pub struct TestPlanTestCase {

    pub id: Option<String>,
    pub extension: Vec<Extension>,
    pub modifier_extension: Vec<Extension>,
    pub sequence: Option<i32>,
    pub sequence_ext: Option<FieldExtension>,
    pub scope: Vec<Option<Reference>>,
    pub scope_ext: Vec<Option<FieldExtension>>,
    pub dependency: Vec<Option<TestPlanTestCaseDependency>>,
    pub dependency_ext: Vec<Option<FieldExtension>>,
    pub test_run: Vec<Option<TestPlanTestCaseTestRun>>,
    pub test_run_ext: Vec<Option<FieldExtension>>,
    pub test_data: Vec<Option<TestPlanTestCaseTestData>>,
    pub test_data_ext: Vec<Option<FieldExtension>>,
    pub assertion: Vec<Option<TestPlanTestCaseAssertion>>,
    pub assertion_ext: Vec<Option<FieldExtension>>,
}

Sub-fields of the testCase field in TestPlan

Fields

id: Option<String>

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.

extension: Vec<Extension>

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.

modifier_extension: Vec<Extension>

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.

sequence: Option<i32>

Sequence of test case in the test plan

Sequence of test case - an ordinal number that indicates the order for the present test case in the test plan.

sequence_ext: Option<FieldExtension>

Extension field.

scope: Vec<Option<Reference>>

The scope or artifact covered by the case

The scope or artifact covered by the case, when the individual test case is associated with a testable artifact.

scope_ext: Vec<Option<FieldExtension>>

Extension field.

dependency: Vec<Option<TestPlanTestCaseDependency>>

Required criteria to execute the test case

The required criteria to execute the test case - e.g. preconditions, previous tests.

dependency_ext: Vec<Option<FieldExtension>>

Extension field.

test_run: Vec<Option<TestPlanTestCaseTestRun>>

The actual test to be executed

The actual test to be executed.

test_run_ext: Vec<Option<FieldExtension>>

Extension field.

test_data: Vec<Option<TestPlanTestCaseTestData>>

The test data used in the test case

The test data used in the test case.

test_data_ext: Vec<Option<FieldExtension>>

Extension field.

assertion: Vec<Option<TestPlanTestCaseAssertion>>

Test assertions or expectations

The test assertions - the expectations of test results from the execution of the test case.

assertion_ext: Vec<Option<FieldExtension>>

Extension field.

Implementations

impl TestPlanTestCase

pub fn builder() -> TestPlanTestCaseBuilder

Start building a new instance

Trait Implementations

impl Clone for TestPlanTestCase

fn clone(&self) -> TestPlanTestCase

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for TestPlanTestCase

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for TestPlanTestCase

fn deserialize<__D>( __deserializer: __D, ) -> Result<TestPlanTestCase, <__D as Deserializer<'de>>::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for TestPlanTestCase

fn eq(&self, other: &TestPlanTestCase) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for TestPlanTestCase

fn serialize<__S>( &self, __serializer: __S, ) -> Result<<__S as Serializer>::Ok, <__S as Serializer>::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for TestPlanTestCase