customized status values?
customized status values?
can you customize/add to the list of status results for each test case? I see a section in the config file with an array that lists some that arent readily available. I would also like to add/change a few of my own. Is this easily achieved?
Re: customized status values?
Yes.fjser wrote:can you customize/add to the list of status results for each test case?
I think "easily achieved" would really depend on how well you can handle the php code, as well as the templates, for you'll have to trudge though the code to cover what you add to the array in the same manner they do. Search for the elements of that array [especially the first four items] throughout the code to see the scope of what files would be involved.fjser wrote:I see a section in the config file with an array that lists some that arent readily available. I would also like to add/change a few of my own. Is this easily achieved?
Hi,
I had managed to reveal the Not Applicable status in the Execution page, but I can't seems to be able to register the results into the database. Meaning that if I select NA for that particular test case, the result will be saved but as BLOCKED.
How can I rectify that? I tried several values in the execNavigator.php but nothing seems to help. I tried:
- $notApplicable
- $NA
- $not_applicable
as values, but to no avail. Can anyone help? I'm not a programmer so I can only figure some codes here and there. Will greatly appreciate that. Thank you.
Johnny
I had managed to reveal the Not Applicable status in the Execution page, but I can't seems to be able to register the results into the database. Meaning that if I select NA for that particular test case, the result will be saved but as BLOCKED.
How can I rectify that? I tried several values in the execNavigator.php but nothing seems to help. I tried:
- $notApplicable
- $NA
- $not_applicable
as values, but to no avail. Can anyone help? I'm not a programmer so I can only figure some codes here and there. Will greatly appreciate that. Thank you.
Johnny
Thanks for replying.
Here's the details of what I have changed:
\lib\execute\execNavigator.php
\lib\functions\exec.inc.php
\lib\functions\results.inc.php
\lib\functions\resultsmorebuild.inc.php
Although it showed on the execute page, but it does not register into the database, meaning results will update as BLOCKED instead of NA. Plus it screwed up the format in the results page.
I hereby attach the files for your reference so that you guys can point out what I had done wrong. Thanks for helping again
The files can be downloaded via http://www.filefactory.com/file/4efc5b/
Here's the details of what I have changed:
\lib\execute\execNavigator.php
\lib\functions\exec.inc.php
\lib\functions\results.inc.php
\lib\functions\resultsmorebuild.inc.php
Although it showed on the execute page, but it does not register into the database, meaning results will update as BLOCKED instead of NA. Plus it screwed up the format in the results page.
I hereby attach the files for your reference so that you guys can point out what I had done wrong. Thanks for helping again

The files can be downloaded via http://www.filefactory.com/file/4efc5b/
Xgrind: I got your files, but please give me time to look at that, for I'm not a TL team member, and I don't have much time during the week to look at it.
I don't mind helping you achieve a customized solution, but also take note of havlatm's previous post:
Havlatm: if I were to put together [offer] a better way to support custom statuses, (all files, DB scripts, etc...) could it be applied as a patch to 1.6, or has the development shift moved on to 1.7?
I don't mind helping you achieve a customized solution, but also take note of havlatm's previous post:
...so there are definitely other files involved. If you would like to continue for your specific need, let me know. Note, though, that the progress would be a little slow from my end.havlatm wrote:... This is not simple patch because the new value must be maintain on several places...
Havlatm: if I were to put together [offer] a better way to support custom statuses, (all files, DB scripts, etc...) could it be applied as a patch to 1.6, or has the development shift moved on to 1.7?
Hi, we can take a look to your code, and implement it or some kind
of modification on TL 1.7.
Please give us enough good information to make our work easier.
It would be great to have some kind of SRS of the feature (may be what is written in this post is enough).
One important thing: we will give to this feature a priority on TL 1.7.x development, because we need to finish test for realesing stable version.
Regards
Francisco
of modification on TL 1.7.
Please give us enough good information to make our work easier.
It would be great to have some kind of SRS of the feature (may be what is written in this post is enough).
One important thing: we will give to this feature a priority on TL 1.7.x development, because we need to finish test for realesing stable version.
Regards
Francisco
Hi Turbo,
I really appreciate what you are doing for me! Thanks!
Ya, I would love very much to have that feature for my side as I used the NA status pretty often before we switch over to Testlink, with that feature it will help us a great deal.
Once again, thanks again for your help!
I really appreciate what you are doing for me! Thanks!
Ya, I would love very much to have that feature for my side as I used the NA status pretty often before we switch over to Testlink, with that feature it will help us a great deal.
Once again, thanks again for your help!

TurboPT wrote:Xgrind: I got your files, but please give me time to look at that, for I'm not a TL team member, and I don't have much time during the week to look at it.
I don't mind helping you achieve a customized solution, but also take note of havlatm's previous post:...so there are definitely other files involved. If you would like to continue for your specific need, let me know. Note, though, that the progress would be a little slow from my end.havlatm wrote:... This is not simple patch because the new value must be maintain on several places...
Havlatm: if I were to put together [offer] a better way to support custom statuses, (all files, DB scripts, etc...) could it be applied as a patch to 1.6, or has the development shift moved on to 1.7?
-
- TestLink user
- Posts: 4
- Joined: Thu Dec 08, 2005 9:04 pm
in TL 1.7 you can customize status.
Only problem:
Reports will not give you info about new status (yet), but you can use
your statuses on execution.
Give a look to config.inc.php and the new file cfg/const.inc.php
You also need to add some CSS classes to show the right colors.
with this code:
$g_tc_status_for_ui = array(
"not_run" => "test_status_not_run",
"not_available" => "test_status_not_available",
"passed" => "test_status_passed",
"failed" => "test_status_failed",
"blocked" => "test_status_blocked");
you add the not_available status to User Interface(UI)
you also need to configure the not_available (is just a code then YOU HAVE NOT USE SPACES in the string) in:
$g_tc_status = array (
"failed" => 'f',
"blocked" => 'b',
"passed" => 'p',
"not_run" => 'n',
"not_available" => 'x',
"unknown" => 'u',
"all" => 'all'
);
hope is clear
Only problem:
Reports will not give you info about new status (yet), but you can use
your statuses on execution.
Give a look to config.inc.php and the new file cfg/const.inc.php
You also need to add some CSS classes to show the right colors.
with this code:
$g_tc_status_for_ui = array(
"not_run" => "test_status_not_run",
"not_available" => "test_status_not_available",
"passed" => "test_status_passed",
"failed" => "test_status_failed",
"blocked" => "test_status_blocked");
you add the not_available status to User Interface(UI)
you also need to configure the not_available (is just a code then YOU HAVE NOT USE SPACES in the string) in:
$g_tc_status = array (
"failed" => 'f',
"blocked" => 'b',
"passed" => 'p',
"not_run" => 'n',
"not_available" => 'x',
"unknown" => 'u',
"all" => 'all'
);
hope is clear