test_outputMessageOwnership

Check the Python interfaces of module-owned output-message collections.

The module remains alive while its borrowed messages, readers, and recorders are used, as in a normal scheduled simulation. Native tests separately check deletion and allocation-failure cleanup; these tests check SWIG access and stable storage.

test_outputMessageOwnership.test_controller_output_growth(module_name, class_name, method, field)

Controller output collections remain usable after adding joints or thrusters.

test_outputMessageOwnership.test_effector_output_growth(module_name, class_name, method, config_name, fields)

Adding effectors preserves state and configuration output-message proxies.

test_outputMessageOwnership.test_environment_output_growth(module_name, class_name, method, fields)

Adding spacecraft preserves existing output addresses and Python access.

test_outputMessageOwnership.test_fixed_output_collections(module_name, class_name, fields)

Constructor-created output collections retain the existing Python API.

test_outputMessageOwnership.test_nested_visualization_outputs()

Nested wheel and thruster collections keep the existing two-index Python API.

test_outputMessageOwnership.test_other_output_growth(case)

Instrument, mapping, ephemeris, and electrostatic outputs retain stable storage.

test_outputMessageOwnership.test_planet_ephemeris_outputs()

Analytical ephemeris messages retain indexing, subscriptions, and recording.

test_outputMessageOwnership.test_reconfigured_outputs(case)

Replacing an output collection exposes the newly configured messages.

test_outputMessageOwnership.test_thruster_output_growth(module_name, attached)

Both thruster-addition overloads preserve existing output messages.