Hello Folks,
I'm trying to solve that issue several times, but it is still a problem for me.
We import our TC via the TestCaseXLSTOXML.xls file. That worked after some problems.
Now our tester are writing new TC directly in Testlink so there are not in the TestCaseXLSTOXML.xls
To make bulk changes by us or our clients we need to export the whole suite, make the changes and import them
to Testlink again.
1.We export the suite to xml.
2.Then we open the xml file with Excel, make the changes and save it.
3.And try to import it to Testlink. But the import failed.
Is there a way to solve this issue? I believe that I missed something, but I don't what it is.
Any ideas are appreciated .
cheers
Zipper
Import <-> Export Test Suite xml Excel
Moderators: Amaradana, TurboPT, TL Developers
Re: Import <-> Export Test Suite xml Excel
>> 2.Then we open the xml file with Excel, make the changes and save it.
Excel is not an XML editor, you need to use a simple text editor or a real xml editor.
In addition for import/export problems, without the xml example no magic can be done
Excel is not an XML editor, you need to use a simple text editor or a real xml editor.
In addition for import/export problems, without the xml example no magic can be done
Re: Import <-> Export Test Suite xml Excel
hi fman,
thx.
But my problem is that I can't "force" a projekt manager to make his bulk changes of
testcases in a xml editor.
For example. A customer would like to get "his" testcases suite export to do same
correcting. He will not use a xml editor to do this. Can you understand my problem
How can I handle this workflow?
thx.
But my problem is that I can't "force" a projekt manager to make his bulk changes of
testcases in a xml editor.
For example. A customer would like to get "his" testcases suite export to do same
correcting. He will not use a xml editor to do this. Can you understand my problem
How can I handle this workflow?
Re: Import <-> Export Test Suite xml Excel
If your project manager can only use excel (as unfortunatelly other people do, because seems this piece of crap is the best tool in the world) we can do nothing.
You need to understand that due to complex structure of test suites and test cases XLS is not an option.
No need for XML editor, notepad++ or ultraedit or sublime can do the trick, if people is clever enough (that means people is willing do a simple job or search and replace, instead of need desperately drag & drop).
At this point you have no solution, than people has stop trying to have a simple (and WRONG) solution for a complex task, people need to use TL native interface.
If this is not acceptable, You will be forced to do or to pay for a custom development.
Excuse me if I can not provide you with a solution
You need to understand that due to complex structure of test suites and test cases XLS is not an option.
No need for XML editor, notepad++ or ultraedit or sublime can do the trick, if people is clever enough (that means people is willing do a simple job or search and replace, instead of need desperately drag & drop).
At this point you have no solution, than people has stop trying to have a simple (and WRONG) solution for a complex task, people need to use TL native interface.
If this is not acceptable, You will be forced to do or to pay for a custom development.
Excuse me if I can not provide you with a solution