When you update a Test Set in Test Lab Module, ALM gives a popup asking you if you want to save changes in the Test Plan as well. So naturally we click “yes”. However, when one goes to Test Plan Module and checks the Test Case, one sees that it does not save updates in the Test Plan! I know this has always been so, but my question is: why is there that popup message if it does not save updates made in Test Lab to the Test Plan?
It should be saving the updates to Design Steps and Expected Results. It always has in my environment. Have you tried refreshing the Test Plan display? If you are not seeing the changes even after a refresh then you may have something else, like custom permissions or workflow modifications, blocking the updates.
I refreshed, relogin etc, and have not seen the changes made in test lab in the test cases on the test plan module.
Circumstances: Assuming you have 3 Test Sets created from the same Test Cases in the Test Plan Module. Now you want to update each Test Sets differently owing to different criteria. Let’s assume you did update all 3 Test Sets.
Now you can see the difficulty QC/ALM runs into if it tries to update the “parent” Test Cases from the Test Sets! Which Test Set it should “listen” to for making the updates?
So it seems like the test cases in test plan module are not update when you make update in the test lab
What exactly have you changed in the Test Lab for the test case? There may be some elements that don't actually get updated back into the Test Plan. I think I've seen that before.
In the scenario where you have multiple Test Instances in the Test Lab referencing the same Test Case in the Test Plan, updates to the Test Plan would occur in the same time order they are made in the lab. So, the last update to be committed from the Lab would be the one seen in the Plan.
If you are making the updates in a truly simultaneous way in the exact same second, I don't know what would happen.
[ QUOTE ]
...Assuming you have 3 Test Sets created from the same Test Cases in the Test Plan Module....
[/ QUOTE ]
I recommend to stay away from having more than one test instance for a test case within a release cycle (even an entire release). The problems you are reporting are new to me (you don't mention what release/PL you run), but there is a lot more trouble waiting for you down the road in terms of built-in functionality that seems not to be linked on first sight.
Are you using version control? It is likely that if you have version control enabled the update won't occur if someone has the test checked out. Similarly you don't see the execution status change when you run a test that is checked out.