TestLink

Hi,
I have successfully migrated (a Copy) of our TestLink 1.7.5 to 1.9.4 .
Now I try to integrate our Jira (v4.3.3#617-r149616) into TestLink with these settings:
If I now set up the TestLink project and open a Test for execution I get a instead of the Testcase (when I do not set up jira).

The <uriwsdl> in the browser gives me an XML-file and the <uricreate> a correct Issue creation page. The http://www.w3schools.com test of the XML-file is ok.
The manual only talks of jira 3.1 -minor upgrades, but there seems to be some people who get it to work with higher versions.

Maybe it is even because of the german version. (be the way, how can I help with translations, there still seems to be lots to do, the notes at the beginnings of Testcases, Execution and Specification...)

Thanks in advance

David

issue is on xml config file.
Please do a test on our demo site (I know you will not be able to connect to jira, but we can check the xml)
maybe simpleXML parser do not like something that w3schools accept

I tried, but its not working. Almost the same error.

Still but the Testcase and the errormessage (IssueTracker not configured ....) is shown underneath.

One other difference I found. The example for the IssueTracker is shown in the Demo, but not here.

Please give a look also to testlink event viewer, I've found some soap errors on demo.

after doing some simple and minor tests, seems that there is an issue with
<uricreate>https://confluence.XXX.de/jira/secure/C ... /uricreate>
if you remove this line the error with ; do not happens

Answer found:
http://stackoverflow.com/questions/4540 ... arse-error

issue is & that has to be replaced with the entity.
We will try with suggested fix on http://stackoverflow.com/questions/4540 ... arse-error

After some tests, my choice is DO NOT TOUCH CODE just add a warning on config sample

More Infos:

instead of using CreateIssueDetails!init.jspa it is better to use CreateIssue.jspa. There you don't need to declare project AND error type, one or none is good.

BUT...

I tried with <uricreate> and without. If I activate the Issue Tracker I get no Testcases in the Test Execution, just a blank frame. On the demo site the Testcase is shown (Project demo, for example), with or without an errormessage.

In the eventlogs I found this warning:
E_WARNING require_once(SoapClient.class.php) [<a href='function.require-once'>function.require-once</a>]: failed to open stream: No such file or directory - in C:\Projekte\Qbase\Testlink\www\testlink\lib\functions\common.php - Line 99

1000 times said but seems useless => do not use forum for issues => use mantis.
this kind of error smell of autoload() failing to load class.

I don't think this is a bug. Your demosite works, but in my installation it doesn't.

similar issue reported on mantis, by user using WAMPP.
Some misconfiguration at PHP include path level or something like that, but have no clear idea

Oh, ok.

So here some update on the system.
It's a virtual machine with Windows XP just for Testlink. Back in 2008, I installed everything "by hand".

Installed on it is:
- MySQL Server 5.0
- PHP 5.2.4
- Apache HTTP Server 2.2.4

No package or anything. Can that be the problem?

user have found SOLUTION ( we are going to add some new check) you have to enable SOAP DDL on your php.ini
see on mantis http://mantis.testlink.org/view.php?id=5278

please check and provide feedback

ok, I am getting close.

I found the php_soap.dll for php 5.2.5 on the net, copied it to the ext folder and added it in the php.ini. Now I can see the testcase.

BUT

the connection is still not working.

I get this:
E_NOTICE SoapClient::SoapClient() [<a href='function.SoapClient-SoapClient'>function.SoapClient-SoapClient</a>]: Unable to find the wrapper "https" - did you forget to enable it when you configured PHP?

I found out, that in PHP ssl is not configured. I added the php_openssl.dll to the extentions and installed openssl for windows, but still no luck. SSL is neither in "Registered Stream Socket Transports" nor in "Registered PHP Streams". I added [PHP_OPENSSL] section to the php.ini and updated the Path-variable. The OPENSSL_CONF variable is shown in phpinfo() and the right Path.

I finally give up. When our release is done and nobody is using testlink for a while, I will backup the DB and install a fresh and current XAMPP. But I can't do it before end of November. I will give an update then.

Thanks a lot, David

use XAMPP if I'm not wrong you will get ALSO HTTPS ready to use