Hello,
My spreadsheet has multiple cases and scripts on one tab for 1x1 linking as users do not care for multiple tabs.
Our naming convention needs to be retained as we start test cases with 'TC_' and test scripts with 'TS_'
My issue is that the test case is getting created with one new section, one named ‘ID’ with text containing the test script name.
From reading Hao’s reply to my previous post it sounds like this new section is being created in support of that one-to-one linking with different names Is that correct?
If so is there any way to programmatically remove these sections after they are created? I am able to update it with informative text but would rather remove it altogether if possible.
It appears that all is okay when I manually remove it so to clean things up I'd like to include removing this new section in this process after linking the artifacts if at all possible.
Or am I still missing something... An updated config is below.
Thanks again,
Scott
-----------------------------------
//Start looking for assets after row 1.
testscript.XLSStartRow=2
testcase.XLSStartRow=2
//A new test script starts when we encounter an empty row.
testscript.XLSDelimeter=\n
//Set the test script name and ID.
testscript.XLSArtifactID=F
testscript.dc:title=F
//Test scripts are not required to be in an approved state in order to run the TER record. Test cases are.
//Importing test scripts as Draft to allow for edits.
//set testscript state to "Draft"
testscript.alm:state ="com.ibm.rqm.planning.common.new"
//Step type is defined within the spreadsheet <== need to add step type column to support reporting steps, TBD.
testscript.steps.type="execution"
//Set the test script description.
testscript.dc:description=G
//Set the test steps description.
testscript.steps.description=J
//Set the expected result
testscript.steps.expectedResult=L
//Link the test case and test script.
//Note: This will create a new section in the test case named 'ID' to store the XLSArtifactID during import.
//This test case section (ID) may be removed after import.
testcase.ID=testscript.XLSArtifactID
//Inform the user about the ID section created above.
testcase.Section("myns:ID","ID")="This section was created in support of the Excel import. You may remove this section."
//A new test case starts when we encounter an empty row.
//testcase.XLSDelimeter=\n
//Set the test case title.
testcase.dc:title=A
//Test Cases need to be in Draft in order to generate TER records from underneath the test plan.
//After genrating TER records mass update test cases to 'Approved. Test cases must be in an approved state to run the TER.
//set testcase state to "Draft"
testcase.alm:state="com.ibm.rqm.planning.common.new"
//Set the test case description.
testcase.dc:description=B
//Set the test case precondition.
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=Pre(D2)
//Set the test case postcondition.
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePostCondition","RQM-KEY-TC-POST-COND-TITLE")=Pre(E2)
//Set the Owner of the test case from Spreadsheet in Domain format (E.g.: AB92383).
//Owner must be entered as configured on the server, and must be a member of the RQM project which assets are being imported.
testcase.jzalm:owner=T
//Set test case weight = 100.
testcase.weight="100"
//System/Subsystem category values should match Barometer IT/ClearQuest values.
//And the category values as defined in the Summary section of the Test Case.
//Import valid test case Lean specific categories.
testcase.category term="Priority".value=S
testcase.category term="Test Cycle".value=U
testcase.category term="System".value=V
testcase.category term="Subsystem".value=W
testcase.category term="Test Type".value=X
testcase.category term="Test Level".value=Y
//Import valid test case project specific categories. Do not alter columns A - Y.
//Uncomment the next line to use. Custom categories may start with column Z.
//testcase.category term="YourCategoryName".value=TheColumnInSpreadsheet
//End of file
---------------------------
Test Script ID
|
Test Script Description
|
Req #
|
Test Script Step #
|
Test Script Step
Description
|
Test Data
|
Expected Results
|
Actual Results
|
Pass/Fail
|
Test Script Status
|
Iteration#
|
Defect #
|
Comments
|
Priority
|
Owner
|
Test Cycle
|
System
|
Subsystem
|
Test Type
|
Test Level
|
TS_Test_Script1
|
Test_Script1_Description_1
|
|
1
|
Test_Script1_Step_Description_1
|
|
Test_Script1_Expected_Results_1
|
|
|
|
|
|
|
2-High
|
ABXXXXX
|
Functional
|
WGS
|
Member
|
SIT
|
User Acceptance Test
|
|
|
|
2
|
Test_Script1_Step_Description_2
|
|
Test_Script1_Expected_Results_2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3
|
Test_Script1_Step_Description_3
|
|
Test_Script1_Expected_Results_3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4
|
Test_Script1_Step_Description_4
|
|
Test_Script1_Expected_Results_4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5
|
Test_Script1_Step_Description_5
|
|
Test_Script1_Expected_Results_5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6
|
Test_Script1_Step_Description_6
|
|
Test_Script1_Expected_Results_6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7
|
Test_Script1_Step_Description_7
|
|
Test_Script1_Expected_Results_7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
8
|
Test_Script1_Step_Description_8
|
|
Test_Script1_Expected_Results_8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9
|
Test_Script1_Step_Description_9
|
|
Test_Script1_Expected_Results_9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
10
|
Test_Script1_Step_Description_10
|
|
Test_Script1_Expected_Results_10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
11
|
Test_Script1_Step_Description_11
|
|
Test_Script1_Expected_Results_11
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
12
|
Test_Script1_Step_Description_12
|
|
Test_Script1_Expected_Results_12
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
13
|
Test_Script1_Step_Description_13
|
|
Test_Script1_Expected_Results_13
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TS_Test_Script2
|
Test_Script2_Description_1
|
|
1
|
Test_Script2_Step_Description_1
|
|
Test_Script2_Expected_Results_1
|
|
|
|
|
|
|
1-Urgent
|
ABYYYYY
|
Regression
|
WGS
|
Member
|
SIT
|
Subsystem Test
|
|
|
|
2
|
Test_Script2_Step_Description_2
|
|
Test_Script2_Expected_Results_2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3
|
Test_Script2_Step_Description_3
|
|
Test_Script2_Expected_Results_3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4
|
Test_Script2_Step_Description_4
|
|
Test_Script2_Expected_Results_4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
5
|
Test_Script2_Step_Description_5
|
|
Test_Script2_Expected_Results_5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
6
|
Test_Script2_Step_Description_6
|
|
Test_Script2_Expected_Results_6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
7
|
Test_Script2_Step_Description_7
|
|
Test_Script2_Expected_Results_7
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
8
|
Test_Script2_Step_Description_8
|
|
Test_Script2_Expected_Results_8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
9
|
Test_Script2_Step_Description_9
|
|
Test_Script2_Expected_Results_9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
10
|
Test_Script2_Step_Description_10
|
|
Test_Script2_Expected_Results_10
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
11
|
Test_Script2_Step_Description_11
|
|
Test_Script2_Expected_Results_11
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
12
|
Test_Script2_Step_Description_12
|
|
Test_Script2_Expected_Results_12
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
13
|
Test_Script2_Step_Description_13
|
|
Test_Script2_Expected_Results_13
|
|
|
|
|
|
|
|
|
|
|
|
|
|