I think, in short, "Test case" is suite of steps (and an expected result) that leads to detect conformity or deviation between expected and actual behavior of ONE application functionality in accordance with requirement, documentation, specification.
I think you have covered the "tip of the iceberg". In my opinion the answer should go quite a bit deeper. That depth is determined by many factors. One of the main driving factors is determined a couple of questions:
1) Are the tests proving correctness of the application?
2) Are the tests showing where the application is not correct?
I'll leave my opinion at that since the total answer often results in writing a book.
What makes mine incorrect? [img]images/icons/smile.gif[/img] [img]images/icons/smile.gif[/img] Incomplete - definitely. I won't be writing a book anytime soon to complete the definition. [img]images/icons/smile.gif[/img]