Follow-up from "WIP: Adding Content protection support in drm-backend"
The following discussion from !48 should be addressed:
@aknautiyal, apropos testing, have you thought about that?
You could have the test suite exercise the protection protocol features by letting the headless backend change output protection status through a small addition to the test protocol extension. You would be able to test the initial protection status, the effect of output status changes, and window movement. You could also test screenshots and maybe (en)forced mode.
Or is that something @ascent could perhaps work on?