The A&C test cases add skip messages for all alarm types that are not encountered. In order for the user to verify that the system is working correctly, it is necessary for them to
1) determine which alarm types they are actually expecting
2) on each test case, on each test run, go through the list of up to 22 skip messages on each test case and check whether all the expected alarm types are not in the list

This is an error prone and time consuming process, which could lead to the user not noticing that the server was not conformant.

It would be more convenient if the user could configure which alarm types to expect, and then only produce skipped (or warnings?) for expected alarm types that were not detected.

This would make the A&C conformance testing more consistent with how static nodes are tested.