Martin Matyáš

to be discussed: should functional tests be part of the testsuite?

remove from "Draft"?

needs rebasing

oran spec tests pass, but they don't work correctly. In fact they should fail, because waiting for CNFs to be deployed does not finish: 

lgtm also now after fixing all issues. Great that all that those tests dependent on default namespaces were identified and fixed.

Can the architecture be made more future-proof towards possible future config versions? - Identify source version of the confing on the input - Have possibility to tell which config version...

Additionally, how about error handling? Like non-supported config keys on input? Maybe other error conditions?

Spec tests need adaptation https://github.com/cnti-testcatalog/testsuite/actions/runs/10455212865/job/28983108223

#2090

My input for the discussion/decision: I propose not to have support for this. Reasons: - The value of this feature is very low: The same results can be obtained by...