What is the relationship between requirements and test cases?

Question

I see that there are many systems for tracking case verification requirements, and I started asking myself what the relationship between the two artifacts is. For example, why the concept of test cases, and not just call them detailed requirements? Are test cases a refinement of the requirements? If test cases are not requirements and require more than documented requirements (for example, testing more errors, etc.), then, of course, are the established requirements incomplete? Are only abstract test cases required?

Answer 1

, , , . , , ? ?

, , , . , . , , .

. , , . ( ) , - , .

, (, ..), , , ?

, . , , .

. . . , , , , , , , .

: http://www.ibm.com/developerworks/rational/library/04/r-3217/

, . , , , , , .

?

, , . , , " ", .

- . , . . , 100% - , 1 . , , . , .

- > , , , .

Answer 2

TDD - .

.

Answer 3

, /.

• Agile (Scrum, XP ) , . , /.

• , , .

• Waterfall , , . . , , CMMI .

Answer 4

a , . , .

, .

Answer 5

. , , , , . , .

, , .

, . - , , - , , . , , , , , .

, , . , , () .

Answer 6

As I understand it, the requirements are somewhat more general than the test ones.

The requirement may be, for example: a method should not accept numbers outside the range of 18-64. Then the test cases may be something like this:

• provides 17 as input
• provides 65 as input
• provide -1 as input

But basically it's a matter of common understanding in the development team ...

Thomas