Coming from software development, we do have tests that insert a screenshot into the report in case they fail, and I'm assuming we are not the only ones that found the PrtScr button to be useful for that
Coming from software development, we do have tests that insert a screenshot into the report in case they fail, and I'm assuming we are not the only ones that found the PrtScr button to be useful for that
I can honestly say you might be the only ones. I've never heard or even conceived of such a thing.
There are a ton of ways to avoid this in the first place:
- use CLI to take the screenshot instead of simulating a key press
- don't test on Windows 11
- use reproducible test instances where you've turned this option off
- (if screenshotting text) use... logs?
I'm truly baffled by this complaint.
I wouldn't put it past Microsoft to preserve the old behavior just for programmatic keypresses.
For 99.999% of the users, I reckon this is a good change. And for the rest they've thoughtfully provided an option to revert.