testsuite
testsuite copied to clipboard
[Feature] Redesign oran_e2_connection test
Currently, oran_e2_connection test requires running Tshark capture during CNF installation, which writes info about e2 connection to the config. During the test - config is read and result is given based on written info.
Problem is that adding complexity to the CNF setup process is not ideal (#2036), and from my point of view - we should find another way to check if cnf is ORAN.