Failed to import Test Step, Test Data & Expected Results

[Keshinee Samarasekara]

Hi,

I tried importing a simple test case using ZFJ.

Log indicated that the import was successful and created a test story in Zephyr but the test step, test data and expected results did not get imported. The fields are empty in the new story created.

Please see ZFJ log screenshot, JIRA screenshot and the test case spreadsheet attached.

Can you please see why it is failing to upload the test case details.

Many thanks

[Christian Gutierrez]

hi! I have the same problem......

[Ashish Lamichhane]

I am having the same issue.

[Test Shamnani]

I am also facing the same issue

[Ashish Lamichhane]

This issue was resolved for me when I used API key (Access key and Secret key) to sign in. You can go to test dropdown, and select API Keys and from pop-up copy access key and secret key and paste into the corresponding importer tool fields. Hope this helps!

[Test Shamnani]

Thanks Ashish! I had tried that but still it is not working for me. Please suggest if there is some other option via which this problem can be resolved

[John Nguyen]

Folks, I can help solve the import issue that you guys are having, but you need to provide the following info: 1- Are you importing test cases to Zephyr in Jira Cloud or the Jira Server? 2 - A snapshot of your input file. A few test cases are good enough. 3 - Full stack trace of the error stack/messages. Also describe to me test-by-step how you capture/use the SSH key, Since the solutions vary on the case-by-case basic, you need to provide your steps in details. The most important thing I need is the stack trace messages.

There are lots of bugs in the import tool. I have filed a bunch of bug tickets to Zephyr but they have not worked to clear out the bugs. The stack trace messages are incorrect and confusing as hell, so don't rely on them. This tool is a piece of trash, J.N

[Former user]

I have the same problem. It worked fine for some period for me but then (I don't know the reason) it stopped working good for me though I've used the correct api keys, credentials, etc. The most interesting thing that other teammates doesn't have the same problem when they follow my instructions

[Dwarakanatha Gandlaveluturla]

Hi John Nguyen, You can find Full stack trace of the error stack/messages in the second snapshot (ZFJ Log.jpg). Is that what you need to solve this issue. Thanks, Dwaraka.

[John Nguyen]

You need to provide all info that I specified in my note. Without those info I will not be able to tell "Where" it went wrong. J.N