coloring in execute tree

The release related discussions, plans and questions.
Locked
jsm
TestLink user
Posts: 11
Joined: Wed Oct 10, 2007 12:16 pm

coloring in execute tree

Post by jsm »

Bug id 0000885 tells that it is possible to bring back the coloring in execute tree by code contributed by Kester Mielke.
But where can I find this code (and how to apply it)?

Need a little mor guidance, sorry for being that clueless.
joerg
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

Code for DTREE and JTREE, up and running on CVS HEAD (thanks to user contribution)
mattias
TestLink user
Posts: 4
Joined: Tue Oct 02, 2007 1:13 pm

Post by mattias »

Yes, this is a must have functionality. Please provide instructions on how to enable this...
jsm
TestLink user
Posts: 11
Joined: Wed Oct 10, 2007 12:16 pm

Post by jsm »

Mattias,

I understood fman's answer in that way that you have to select either DTREE or JTREE in config.inc.php (or better add the belonging section to custom_config.inc.php).
Unfortunately in my case this leads to an error (see Issue 1217 in Mantis).
Does it work if you try?

regards
Joerg
mattias
TestLink user
Posts: 4
Joined: Tue Oct 02, 2007 1:13 pm

Post by mattias »

As I understood, the code is in HEAD. I.e. the code does not exist in 1.7.*-versions.

We have just finsihed a test period and it's really disturbing to not see which test cases are passed/failed/blocked. Besides the coloring 1.6 had a summary within brackets (for each suite) that showed how many was passed,failed and blocked...
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

Ok, but on 1.7.x you have a LOT of things you do not have on 1.6.3, and seems are not important for you.

Adding code to 1.7.x will be done, but you can add yourself using code present on Mantis contributed by Kmielke.

Regards
mattias
TestLink user
Posts: 4
Joined: Tue Oct 02, 2007 1:13 pm

Post by mattias »

I am overall please with 1.7 :-)

How do I add this functionality?
jsm
TestLink user
Posts: 11
Joined: Wed Oct 10, 2007 12:16 pm

Post by jsm »

- Backup your install directory (just in case...)
- get nightly tarball from http://testlink.org/cvs_tarballs/index.php?dir=head/
- expand it over your installation
- check if your customisations are still there
- if neccessary add
$g_tree_type='TREE';
or
$g_tree_type='LAYERSMENU';
in config.inc.php (or better in custom_config.inc.php)

this is the way it worked for me.
hope that helps
fman
Member of TestLink Community
Posts: 3123
Joined: Tue Nov 15, 2005 7:19 am

Post by fman »

For mattias:

1. your attention please HEAD is Alpha code
2. if you do not have done this yet, please take 5 min to add your company to forum
davila
Advanced user
Posts: 28
Joined: Tue May 16, 2006 3:11 pm

Post by davila »

Are there any tricks to getting the older view back when executing test cases (not the tree (left), but the test case view (right)). Thanks.
davila
Advanced user
Posts: 28
Joined: Tue May 16, 2006 3:11 pm

Post by davila »

So, I'm trying the suggestion by jsm and have the latest from HEAD (yep, alpha code). The following warning message appears and number two is a bit confusing, any additional explanation would be appreciated.

Warning!!! Warning!!! Warning!!! Warning!!! Warning!!!
You have requested an Upgrade, this process WILL MODIFY your TestLink Database
We STRONGLY recommend you to backup your Database Before starting this upgrade process

Attention PLEASE:
1. The name/title of testcases, categories, ecc WILL BE TRUNCATED to 100 chars
2. Components and Categories present in Test Plans BUT NO MORE PRESENT IN PRODUCTS
WILL BE DELETED

Warning!!! Warning!!! Warning!!! Warning!!! Warning!!!
havlatm
Member of TestLink Community
Posts: 940
Joined: Mon Oct 31, 2005 1:24 am
Location: Czech

Post by havlatm »

Davila,
do not mess topics.
The second sentence of warning means that previous versions could left some obsolete data in your database. The next conversion will provide some clean-up of such data.
Locked