It's all about the answers!

Ask a question

How to resolve RQMImporter "Input string not in correct format" issue?


Karen Bown (275) | asked Apr 29 '16, 2:58 p.m.
I'm working on creating "cfg" files to work with a word document for my test case and test script. I'm looking at the test case first and have created a "cfg" file based on research and review of the sample files.

When I try to export to repository I get the following error:

Error when parsing artifacts from the document: Input string was not in a correct format.

My "cfg" looks like this:

// This configuration (cfg) file will create/update a single test case based on
// the associated .doc or .xls file. The matching <testcase>.doc or <testcase>.rtf
// file defines the specific information to go in the RQM test case.
// The “<rqmtype>.DOCTableStartRow” or “<rqmtype>.XLSStartRow” line indicates where
// the script starts to read the information from in the .doc or .xls file. The
// "Table(#)" references are to represent the tables in the .doc file in
// numerical order. If a table is added in the middle of the .doc file, the
// associated test case and test script "cfg" files will need to be updated. NOTE:
// The first test case table in the .doc file is informational only and is not
// referenced in this "cfg" file.

testcase.DOCTableStartRow=Table(2).2
testcase.ID=Table(2).C2
testcase.dc:title=Table(2).C3
testcase.dc:description=Table(2).C4
testcase.alm:owner=Table(2).C5
testcase.category term="Test Phase".value=Table(2).C6

// The following custom sections are used to define the full test description,
// pre-requisites, software, and outline. The
// ("<Unique Identifier>", "<Custom Section Name>") comes from a POST in a GET Request.

// testcase.Section(“myns:<Unique Identifier>”, “Test Description”)= Table(2).C7
// testcase.Section(“myns:<Unique Identifier>”, “Test Preparation”)= Table(2).C8
// testcase.Section(“myns:<Unique Identifier>”, “Outline”)= Table(2).C9

I'm choosing to use a word file because we have more data to upload than excel will allow per cell.

My word file has the following:

Test Case Information: The Column/Row reference will be used in the “cfg” file. Anything entered in Column C will be uploaded into RQM.

 

Table 1

A

B

C

2             

Test Case ID

Get the “Test Case ID” from RQM after the test case has been created

3             

Test Case Title

The name of your test.

4             

Test Case Description

Brief description about the test; recommend using the SSS section the requirements are housed in.

5             

Test Case Owner

Who is responsible for this test?

6             

Test Case’s Test Phase

Which test phase will this test case be in?

7             

Test Description Section

Use the default text in the table and update where needed.

8             

Test Preparation Section

Use the default text in the table and update where needed.

9             

Outline Section

Use the default text in the table and update where needed; keep it in outline format.

 

Fill in this table with the test case specific information to update RQM with. RQM keeps a history of all changes so there is no need to keep track in the work document itself. Keep the column and row labels the same; do not change. The only data to be updated is the cells in white.

Table 2

A

B

C

2             

Test Case ID

57

3             

Test Case Title

RQM Importer Test

4             

Test Case Description

Testing how the RQM Importer works

5             

Test Case Owner

Karen Bown

6             

Test Case’s Test Phase

System

7             

Test Description Section

This test will verify the requirements associated with the <section of the SSS where the requirements(s) are found> using <specify a product, tool, etc that will be used for verification>.

8             

Test Preparation Section

The following items are required for the verification of this test:

 

·         <Software Release>

·         Detailed workstation configurations (i.e. ATL, SLC if necessary) including identification of workstations that will utilize the OSS Portal, Web Services, a test tool, etc.

·         Any other test procedures that should be executed prior to executing this procedure; include test number.

·         Any test tools that are needed to execute the procedure (i.e. SoapUI, Smartbear…).

·         Specific personnel that are required above and beyond the normal group; such as "Systems Engineer"; "System Administrator" if root access is required.

·         Where applicable, what internet browser(s) will be used for testing?

9             

Outline Section

The following outline provides a high level overview of the verification for this test:

 

 I.    <Insert outline; Action statement>

       A.    <Insert outline; Verification statement; AIMMS2Req-###>

       B.    <Insert outline; Verification statement; AIMMS2Req-###>

II.    <Insert outline; Action statement>

       A.    <Insert outline; Verification statement; AIMMS2Req-###>

       B.    <Insert outline; Verification statement; AIMMS2Req-###>


Thanks for the help!

Karen

Accepted answer


permanent link
Mehul Patel (6694) | answered May 02 '16, 5:16 a.m.
FORUM MODERATOR
Karen,

The first line syntax is incorrect -
testcase.DOCTableStartRow=Table(2).2 <---

Either you can specify start of data row with a literal value or a Table cell representing that value, i.e.
testcase.DOCTableStartRow=2
OR
testcase.DOCTableStartRow=Table(2).B2

Hope it helps.

Regards,
Mehul
Karen Bown selected this answer as the correct answer

Comments
Karen Bown commented May 03 '16, 7:55 a.m.

Hi Mehul, I used the "testcase.DOCTableStartRow=Table(2).B2" option. That definitely helped me get past the first hurdle. A couple of things happened:

  1. It created a new test, 59, instead of updating the existing test 57.
  2. It added two new sections to my test case "DOCTableStartRow" and "ID".

Thoughts on what happened?

Thanks, Karen

One other answer



permanent link
Karen Bown (275) | answered Jun 20 '16, 10:33 a.m.
The additional items can be tracked through RQM Defect 152996.

Your answer


Register or to post your answer.