Notwithstanding the observation made by others (this cites a bug report), in very simplistic terms, a test result is one item of information: Pass or Fail
But what do we mean by Pass? Well, the test performs as expected... ie Actual Result = Expected Result.
The only way a test tool knows the Expected Result is for the tester to specify it - or for the test ...
If one is working for a software testing solutions provider, then a strong focus should be given on exactly how the functionality of a software should be.
And writing exactly how the expected outcomes should be is one of the best ways to go.
Also, when writing a defect, it should be clearly mentioned what the actual outcome in comparison to what the expected ...
Execution of test cases is not big concern for QA guy. Big issue is how to write them in proper way (i.e. DRY which was already said by Cronax).
The issue's impact depends to the product's scope. Let's supposing that there are 3 different action and 19 different page for all roles. A role can edit or view or not see that pages. In this case, I think test ...
"The essence of strategy is choosing what not to do."- Michael Porter
Everything in testing eventually comes down to one question- how it may affect business, as testing is fundamentally risk driven activity.
As with any effective strategy, an test strategy should not only cover what to test but more importantly what not to test.
As illustrated ...
"The value of any practice depends on its context"
N-wise testing is a technique, not a silver bullet to solve any problem.
It's your responsibility as a professional to analyze how to best approach a specific problem.
Take the example of a pairwise analysis:
valid name, valid password
valid name, invalid password
invalid name, valid password