MantisBT - TestLink
View Issue Details
0003486TestLinkasimon_thesispublic2010-05-25 11:062010-07-02 18:35
Falcon1 
asimon 
normalminoralways
closedfixed 
1.9 Beta 4 
1.9 Beta 5 
0003486: In the execute page, tree doesn't update when you change "Test Plan" in the "Setting" panel
If you have two test plan with two different builds (or more) for each Test Plan, in the execute page when you change Test Plan in the Setting panel and then you click on a test case in the tree, although Update tree after every operation is checked the build doesn't update. So if you save an execution for that test case the build saved on database can be wrong (see 0003451:0010142)
- Create Test Plan Test01 (make it Active and Public) with one test suite (for example TS01) that has two test cases (for example TC01 and TC02). Add these test cases to Test Plan Test01.
- Create Test Plan Test02 copying from Test Plan Test01.
- Create two builds for Test Plan Test01 (for example 1.0.0 and 1.1.0) and two other builds for Test Plan Test02 (for example 2.0.0 and 2.1.0).
- Choose Test Plan Test01 in the section Current testplan: of the main page.
- Click on Execute: in the Setting panel the Test Plan must be Test01 and the Build to execute must be 1.0.0. Check the option Update tree after every operation if unchecked.
- Click on the first test case of the tree (in this example TC01): in the main screen you can see the information about that test case, with correct build version.
- Change the Test Plan in the Setting panel and choose Test Plan Test02. The combo Build to execute will be update correctly to build 2.0.0.
- Without clicking any other button or option, click again on the first test case of the tree (in this example TC01): in the main screen you can see that the information about the build is wrong. If you save the execution, in the database the result will be saved with the wrong build.
No tags attached.
related to 0003451closed asimon In the "Test reports and Metrics" -> "Test report" the "Last Result" is always "Not Run" 
Issue History
2010-05-25 11:06Falcon1New Issue
2010-05-25 18:06fmanNote Added: 0010144
2010-05-25 18:08fmanRelationship addedrelated to 0003451
2010-05-25 18:09fmanRelationship addedrelated to 0003487
2010-05-26 06:33asimonNote Added: 0010152
2010-05-26 06:33asimonAssigned To => asimon
2010-05-26 06:33asimonStatusnew => assigned
2010-05-26 16:00asimonCategoryTest Execute => asimon_thesis
2010-06-25 11:20asimonNote Added: 0010426
2010-06-25 11:20asimonStatusassigned => resolved
2010-06-25 11:20asimonFixed in Version => 1.9 Beta 5
2010-06-25 11:20asimonResolutionopen => fixed
2010-07-02 18:35fmanNote Added: 0010477
2010-07-02 18:35fmanStatusresolved => closed
2010-07-23 14:54asimonRelationship deletedrelated to 0003487

Notes
(0010144)
fman   
2010-05-25 18:06   
Reminder sent to: asimon

would you mind to give a look ?
(0010152)
asimon   
2010-05-26 06:33   
This belongs to my work, I'll take care of this error while refactoring.
(0010426)
asimon   
2010-06-25 11:20   
Solved in CVS. Please retest with next available beta version, feel free to reopen issue if needed.
(0010477)
fman   
2010-07-02 18:35   
1.9 Beta 5 released