LUMIERA.clone/tests/16parameter.tests

TESTING "Library Test Suite: parameters" ./test-suite --group=param


PLANNED "Parameter Values" Parameter_test <<END
return: 0
END


PLANNED "Parameter Domain Type" ParameterDomain_test << END
return: 0
END
Parameters: start a design draft Parameters and Automation will certainly play a crucial role eventually. They will form a network of relationships to cover all further concerns that can not directly be conceptualised as arrangement or processing. A shift in the setup of the Job-Functor arguments necessitates to introduce a `Parameter` type — ''albeit just as placeholder'' 2026-07-01 01:50:26 +02:00			`TESTING "Library Test Suite: parameters" ./test-suite --group=param`



			`PLANNED "Parameter Values" Parameter_test <<END`
			`return: 0`
			`END`
Parameters: preliminary requirement analysis In the current stage, a design-draft is required that is sufficiently adequate to be used as code placeholder and to evolve into the full specification eventually. - we need a single parameter container type with value semantics - parameters must support a selection of basic value types, with conversions - the value range can be limited, and a parameter can be associated with a ''Scale'' (stepped, continuous, logarithmic) - a parameter can be linked to a functional source - parameters are (virtually) copyable 2026-07-03 19:55:55 +02:00

			`PLANNED "Parameter Domain Type" ParameterDomain_test << END`
			`return: 0`
			`END`