Error Importing test scripts into RQM using RQM Excel Importer: (400) Bad Request
Hello,
I am using CLM Suite 6.0.6 ifix003
I am importing test scripts into RQM via the excel rqm importer add-in. I attempted importing 40 seperate test scripts and test cases with a 1 to 1 relationship. 7 of the test scripts refuse to import and always throw this error:
Within the RQM Export Dialog Box:
Sending testscript 2 named Fires_Capabilities...
Error sending to server Fires_Capabilities of type testscript
The remote server returned an error: (400) Bad Request.
Within the log file generated from the export:
11/5/2018 7:36:27 AM: sending testscript0 named Fires_Capabilities
11/5/2018 7:36:27 AM: Server returned code BadRequest
11/5/2018 7:36:27 AM: Error sending to server Fires_Capabilities of type testscript
11/5/2018 7:36:27 AM: Bad Request
Since 33 of the test scripts import correctly, I know the formatting of the excel file is correct, and the .cfg file is working correctly. Bad Request gives no insight into what is erroring out, I am at a loss.
For visibility this is my .cfg file:
// This configuration file creates a test case with each test script and links them.
// The linking is accomplished by self referential data
// Start looking for scripts after row 2
testscript.XLSStartRow=2
// use the data in the first row of a found script's column B
testscript.XLSArtifactID=F
testscript.dc:title=F
testscript.dc:description=B
// the literal "execution" will be put into the step type tag, so all steps will be of type execution
testscript.steps.type="execution"
testscript.steps.description=RichText(H)
testscript.steps.title=G
testscript.steps.name=G
testscript.steps.expectedResult=I
testscript.steps.comment=J
// a new script starts when we encounter an empty row
testscript.XLSDelimeter=\n
// we want to use the data we got for each test script to create a test case
testcase.ID=testscript.XLSArtifactID
// by referring to the testscript's field instead of the column that data comes from
// the tool will also create links to each of the test scripts.
testcase.dc:description=testscript.dc:description
testcase.dc:title=A
testcase.Section("com.ibm.rqm.planning.editor.section.testCasePreCondition", "RQM-KEY-TC-PRE-COND-TITLE")=C
testcase.Section("com.ibm.rqm.planning.editor.section.testCasePostCondition", "RQM-KEY-TC-POST-COND-TITLE")=D
testcase.category term="Project".value=E
Any help is greatly appreciated, this is actually time sensitive. Thanks in advance!
|
2 answers
Is it possible to get a snippet of your Excel file? An example of a Testcase that imported correctly and another that didn't import correctly?
I have no idea if you're just getting lucky with the other 33, but I don't think you need this line:
testcase.ID=testscript.XLSArtifactID
Your test cases are already linking to the test scripts with this line:
testcase.dc:description=testscript.dc:description
testcase.ID has had some issues in the past, but they were supposed to be resolved as of 6.0.4
|
Timothy,
As you are facing failure for particular test script, it appears to be data specific issue. I would check it
- By exporting data to local file and check generated xml for that specific test script, if it reveals some obvious anomaly.
- Sometime RichText might not handle microsoft specific formatting tag, I would try removing the RichText call from cfg file.
In case none of above works then as Don suggested contact support with the data and they can assist.
Regards,
Mehul
|
Comments
The qm.log reads as follows:
It looks a bit different, but you might want to discount this issue as a possibility:
https://jazz.net/jazz02/web/projects/Rational%20Quality%20Manager#action=com.ibm.team.workitem.viewWorkItem&id=172319
I appreciate the response Ian, unfortunately all of the test scripts had the same naming convention and same goes for the test cases. So if there was potential for a certain character within the names to cause an error, I believe it would have errored for every test script in the import as opposed to only a handful of them.