incremental imports

[haacee]

Hi,

we want to generate our testlink testcase entries from some form of documentation.
This is quite easy initially using xml as an intermediate format.

However when I import the same xml file twice I duplicate all entries. This is not the intended use for us.
When a testcase is already defined within a testsuite it should be ignored on the second import.
This seems to be deliberately implemented since the sequence export-from-testlink, import-to-testlink yields the same result.

I am not sure whether this behaviour is specific to testlink 1.8(.3), since I am new to testlink and have only seen this version.

Is there anyway I can influence this behaviour, without going through the hassle of diffing an up-to-date export with my input?

Regards,

Erik van Veelen

[fman]

same old story all the time

1. do not use forum for things you consider issues => report it on mantis
2. 1.8.x has reach End Of Life => Dev team does not support it anymore => get 1.9.1

[haacee]

If you read my post careful I was not claiming this to be an issue.
I was asking for the possibilities within the tool.

If this is the normal level of support you are providing, I for one will not be a supporter for an upgrade, but would strongly recommend changing the toolsuite!

Hope this was a one time thing........

[fman]

>> When a testcase is already defined within a testsuite it should be ignored on the second import.
This sentence means to me that you consider it an issue.
But waht is the offending part of asking to use Mantis for issue requests?
On older versions like 1.8.3 ( that is not the last on 1.8.x line) development team will not spend time.

And finally if you do not like how we work/help , no problem change tool ASAP

[haacee]

Maybe I was a bit harsh. But I got the feeling that my problem (being an issue or not, left aside) was not taken seriously.

What I meant to say with "This is not the intended use for us" is that we do not want that behavior. If that behavior is by design, it is not an issue. If it is not the design than it would be an issue.
My apologies for the misunderstanding.

I was merely asking for the possibilities already present in the tool (being it in 1.8.x or another) to implement my requirements.

Hope you can provide me with details on the approach used in testlink (and it's underlying dB engine) for the import functionality.
The documentation only provides the 'simple' scenario's.

[fman]

As stated before best option is at least install 1.9.1 because there are options to update content when system find a duplicate testcase.
Several options are also available to say 'test case is duplicated'
This can be first step before trying upgrade.
We do not have enough 'working force' to maintain good docs, then users have to learn by exploring, unfortunatelly