You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test documentation should not indicate that a check may be performed in a test step if that check will never be performed in that test step. So, it's ok (for instance) for there to be a lot of gray checks for NET0730 because notifications could be performed in any of those steps, it's just that there were no notifications to deliver because there were no entities to delete in the nominal case. But, it seems like the "Slow updates flight" test case of the "ASTM NetRID Service Provider operator notification under slow update rate" test scenario documents that it will perform many checks that it does not actually perform -- for instance, it seems like the gray checks in NET0710,1 should not be conditional so they should either be performed or else not documented as part of the scenario. There is also a lot of gray for DSS0030,a. It's ok to remove a lot of documented checks -- we don't need to check everything we possibly could at every possible opportunity. But, when a regulator asks why a particular check wasn't performed in a given test run, we should be prepared to give a good answer (as above in the NET0730 case).
The text was updated successfully, but these errors were encountered:
As reported by @BenjaminPelletier on 2025-02-12:
The text was updated successfully, but these errors were encountered: