OK with something like "As `orElse` often represents a default value that is typically not exercised in normal usage, enforcing test coverage of these alternative code paths is worth considering."? Just inverting so the reason for being strict(er) about code coverage is stated first...