Page History

...

• Clone Tests and use the "data" column to put the values for the inputs of each partition/class
• If doing Equivalence Class Partitioning, don't specify exact values for the class, to have some randomness; if later on you find a bug, you may create a Test case with the exact value to verify the fix

Few Tests (or few testing) per requirement

A requirement covered by few test cases may be a symptom of lacking test cases, testing only the successful path.

• Create more Tests using white and black-box testing related techniques

...

Promote reusability and avoid cloning Tests specifications

If Tests are exactly the same, in theory there should be no need to have clones.

Whenever talking about clones, we may be talking about explicit clones (i.e. cloning the whole Test issue, with all its steps) or implicit/embedded clones (i.e. where the steps of an existing Test are used in another more high-level Test case). 

If you are thinking on using Tests as steps in other more high-level Test case you should consider modular tests and not using implicit/embedded clones.

In general, users may clone Tests for different purposes:

...