Edit/Delete Test plan is not possible

[paddyk]

We recently migrated from 1.5 to 1.6 of Testlink and we have the following problems
1. Test plans created by one user cannot be seen by another user (both users are admin). We got around it by manually editing the projrights table and putting a (userid, projid) combination for each user. That is now working correctly.

2. I actually need some help with issue number 2. On the main page, I can see the drop down Test Plan where I can see all the test plans. But when we click the Edit/Delete Test Plan link (under the "Test Plan Management" link) and then navigate to the "Edit/Delete" tab on the subsequent page, I don't see any test plans. In fact, there is a line which says "There are no Test Plans defined!" even though
a. There are test plans defined and we can see those in the drop-down on the main page. and,
b. In the database, I can see ALL the test plans in the projects table.

Appreciate any help.

Thanks in advance,
- K

[Andrew]

Hi there!

I am also encountering the same issue as paddyk and need assistance. I too have upgraded from a previous version, in my case from 1.0.4 to 1.6.2.

On upgrade we needed to manually assign Product ID's (prodid) to the Project table in the place of the default "0" that was entered in upgrade.

The projrights table also required manual manipulation to view certain test suites (nee plans).

I too have issues with the section entitled "Test Suite Management". In 1.0.4 when I select the "Edit/Delete Test Suite" I am advised that "There are no Test Suites defined!"

Another section I am having issues with is the "Define User/Project Rights" section. In 1.0.4 I am presented a screen with "User" and "Project" boxes on the side and in 1.6.2 a drop down box offers to switch between Users and Test Suites;

- if I select a user in 1.0.4, a list of active test plans are displayed ... in 1.6.2 when a user is selected, a check box beside "Filter Test Suites by Product" above 3 buttons "Save" "Check All" "Uncheck All", yet no Test Suites.

- if I select a project in 1.0.4, a list of the users is displayed, but in 1.6.2 no Test Suites are displayed at all!

Is there a configuration issue I have not yet addressed?

Any hints and tips would be helpful

[Andrew]

I just noticed another thread "Cant assign test suites to users" which doesn't appear to have received any resolve (last commented on in July) which relates to the second part of my above comment regarding the "Define User / Project Rights".

It would be really appreciated if these issues could be addessed in this forum as I believe it is a useful resource for us users of testlink, for problem solving when problems are encountered particularly when upgrading. However not all of the issues raised have (in my mind) had completed resolutions published for the those of us coming into the same issues months later.

Thanks for the good work guys. Help is much appreciated.

[pvkamath]

I tried fishing through the source code for the solution. It was not clear to me where the editing in done in the planEdit.php (Also didn't help that I haven't worked with php at all

So, I tried looking in the database and I couldn't see any tables related tp plans. I am pretty sure, we messed up the tables when we upgraded.

Again, if anybody has any information in this matter, I would really appreciate it.

Thanks,
Kamath.

[Andrew]

I found on another thread Edit Test Suite a comment by havlatm.

Which version of TL and MySQL are you use? Do you have configured UTF-8?

This prompted us to investigate this and found that somehow we had upgraded with an incorrect collation and Charset of latin-swedish instead of UTF8-general

This may have been caused during an upgrade of MySQL from 3.5 to 4.1. After much hair pulling, we have managed to get the options of "Edit/Delete Test Suite" and "Define User / Test Suite Rights" to operate as expected.

I hope this helps anyone who may encounter this issue in future.

[pvkamath]

Hi Andrew,

Can you give us some details regarding how you got that to work ? I looked in the ini file for MySQL and found that we are using
"default-character-set=utf8"
So, I believe we may have another problem.

We are using version 4.1 of MySQL and version 1.6.1 of TestLink.

Thanks,
- Kamath.

[Andrew]

Kamath,

Here's pretty much what we did, except we were also merging 2 databases into one, so a little additional work was required.

Dump the database to a script using the mysql utility.

Create a new database making sure you choose the correct charset and collation. Check the dump file, making sure the create table commands do not have a charset/collation. Then reload the data, and point testlink at the new database.

Good luck, I hope this helps you resolve your issues.

Andrew.

[pvkamath]

Hi Andrews,

Thanks a lot. Changing the encoding seems to work great and we can now edit/delete test plans. Thanks again for the help.

- Kamath.