TestLink

Hi

Any updates on this ?

Thanks
Rajeev

Let me add more clarity to what I did to see this: 1. Test name 'xx 1' is already executed atleast once (please notice the space between xx and 1) 2. Go to test specification 3. In the tree click on the test 'xx 1' (I would like to rename this test to xx1 without space. Since this test is already ex...

In version 1.9.3, the test plans where the test case has been added takes it automatically when there is a newer version of that test.

So, I guess, you need not worry about it.

Rajeev

Testlink version is 1.9.3.

Feature: update test case using API reportTCResult. As mentioned earlier, I have all the arguments needed for this call to succeed.

Not sure under what circumstances, this problem occurs. Please take a look.

On one of the projects, we are getting this error message: [{'message': 'Test Case (name=xx/id=) is not associated with Test Plan (name=tt/id=5314).', 'code': 3030}] However, I'm sure that the test case has been associated to the test plan being executed and the tests appear in Test execution. Testp...

Hi Haven't searched on Mantis, but we worked around the problem by deleting the plan and setting up a new one. There are no steps to reproduce. However, I can say that this happened after we imported testlink db over 2 times from one machine to another and another. The problem was found with the spe...

Hi, createTestSuite API available in the testlink_api.py fail allows us to create a TestSuite under a Project i.e the root node of the project. It takes arguments as project-id and test suite name. Is it possible to create a test suite under a test suite via API? If the functionality exist , please ...

---------------------- For a Project, we manually created few builds and ran regression against those build-ids. When we tried to delete few builds which are manually created, one of the builds deletion failed with the following error message: ********************************************************...

Ok. This seemed to work. I uncommented and added the schema owner in: define('BUG_TRACK_DB_SCHEMA', '[CONFIGURE_BUG_TRACK_DB_SCHEMA]'); Secondly, I commented out: define('BUG_TRACK_DB_CHARSET', '[CONFIGURE_BUG_TRACK_DB_CHARSET]'); Our db charset is SQL_ASCII which probably isn't supported by testlin...

It's not very different. You use psql -h hostname -U username dbname to connect. Once you login, SQL remains the same. And yes, I'm using the same user and since I'm able to login to bugzilla DB remotely from testlink host using command line, it means that there is no restriction on that host. Looki...

I remember this used to work well with Testlink 1.7.4 when I used it in another company. It used to work without these additional entries. I need to get this working as I have sold the benefits of Testlink very strongly to my management and the option to tie in a bug number to a failed test was one ...

I am able to remotely connect and execute queries on bugzilla db from testlink host using a psql client session. Any thoughts?

Thanks

Hi I am trying to configure Testlink 1.9.3 on host x to talk to bugzilla on host y . Please note both testlink db and bugzilla db are 'postgres' . Not that it should matter. With the initial configuration as per testlink 1.7.3 documentation, I'm able to see the bug icon. On clicking the icon a popup...

I managed to get this working eventhough I'm not an expert with LDAP configuration. I used the resource details from one of our current configurations for a product which uses ldap authentication. The errors I saw primarily because of a wrong ldap_organization setting: ------------------------------...

Oh. That's great.

I'll check it out.

Thanks
Rajeev