What are some different styles of writing test cases? [closed]

Personally, I find the style of writing a test case is irrelevant as long as the essential information for it is there:

• Who will be performing the test - the level of detail I use will be different for a test that's being performed by an experienced tester than for one that I expect a novice tester to perform. I'll give more guidelines to a novice and use more shorthand for an experienced tester.
• What the test needs to do - again, the level of detail will vary.
• What the result should be. This is usually not something I describe in painstaking detail because my test cases tend to be more guidelines for exploration than step-by-step "click this button" type things.
• When the test should be performed - including any prerequisites for the specific test. The nature of software development means I'll often use a single sequence of actions to verify multiple things at once.
• Where in the application and in the test environment the test is being performed - including the need to use a hardware lab, the need to access the application via the Internet rather than from a locally hosted instance and so forth. I've tested in situations where all of these factors are involved.
• Why the test is being performed - this could be as simple as there being a requirement that the software does X, therefore I have to test that the software does X. It could also be a lot more complex and based around what I know of the application user base (is this feature only accessible to specific users who will always be trained, or is it open to the general public?)
• How the test needs to be performed - mostly this is implicit, but there are times when it's necessary to specify that the test needs to be done with keyboard entry or via touch-screen or... You get the idea.

All these factors go into what I write in a test case, which is usually in the form of stripped down notes.