Best practice when major change in product?

The release 1.6 is going to be unsupported by Community. Because our effort moves ahead. However there are still valuable informations for you.
Locked
Sofiane
TestLink user
Posts: 4
Joined: Thu Jan 18, 2007 7:33 pm

Best practice when major change in product?

Post by Sofiane »

We are using testLink since two months.
Actually we will start developing a new version of our product with major changes to our GUI and new functions (from 1.1 to 1.2), which require rewriting more than 50% of our test cases and adding new ones.
My question is what is better with TestLink, I think that I have to decide between these two solutions:
1- Keep same product, add key word "version 1.2" to all old and new test cases used with this version, and include them in a new test plan (with its new builds).
Or
2- Create a new product, name it "Product 1.2", Import needed testcases from current product, add new testcases, and go on.
what is the best?
Sofiane
Locked