How to share same test script on multiple test case imports
I have several hundred test cases with multiple test scripts defined in excel spreadsheets. I am planning on using the Excel Importer to load these all into RQM 2.0.1.1. However, when I to a test import of 2 test cases, each test script for each case is created.
The example:
tc1 has scripts Login and Change Password
tc2 has scripts Login and Help
2 Login scripts (exactly the same) get created.
Is there some way to tie the Login scripts together so that tc1 and tc2 point to the same script and only 1 Login script is created?
My testcase.cfg file looks like:
Note the commented out requirements section. Is there a way to be able to turn that on so it will link a requirement (identified by the artifact ID in D7 of the excel spreadsheet) that matches an existing requirement artificat ID?
The example:
tc1 has scripts Login and Change Password
tc2 has scripts Login and Help
2 Login scripts (exactly the same) get created.
Is there some way to tie the Login scripts together so that tc1 and tc2 point to the same script and only 1 Login script is created?
My testcase.cfg file looks like:
// this configuration file creates testscripts with testcases using self referential
// and column based data with categories
// Start looking for scripts after row 7
testscript.XLSStartRow=8
testscript.XLSWorksheetID="Testcase-Testscript"
testscript.XLSDelimeter=\n
// a new script starts when we encounter an empty row
testscript.dc:title=A
testscript.dc:description=B
// step type is defined within the spreadsheet
testscript.steps.type=C
testscript.steps.description=D
testscript.steps.title=D
testscript.steps.name=D
testscript.steps.expectedResult=E
testscript.steps.property name="comment"=F
// setup the requirement
//requirement.dc:title=B1
//requirement.dc:description=D
//requirement.alm:owner="tmcstraw"
//requirement.dc:creator="tmcstraw"
//requirement.priority=F6
//requirement.tags="$" & D4 & " " & F3 & " " & F4 & " " & F1
//requirement.XLSArtifactID=D7
// self referential links must be declared before also using column definitions
testcase.dc:title=B1
testcase.dc:description=B2
testcase.weight=D1
testcase.dc:creator=F5
testcase.alm:owner=F5
testcase.XLSArtifactID=D5
// Categories are defined in a special way
testcase.category term="Category".value=D2
testcase.category term="Function".value=D3
testcase.category term="Test Phase".value=D4
// Sections are defined differently, the first part within the quotes is the section tag, and the optional second part after the comma
// defines the name of the section. Sections that already defined within RQM will use the display name they already have
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","RQM-KEY-TC-DESIGN-TITLE")=B3
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=B4
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePostCondition","RQM-KEY-TC-POST-COND-TITLE")=B5
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseExpectedResults","RQM-KEY-TC-ACCEPT-CRITERIA-TITLE")=B6
testcase.XLSLink=testscript
//testcase.XLSLink=requirement
Note the commented out requirements section. Is there a way to be able to turn that on so it will link a requirement (identified by the artifact ID in D7 of the excel spreadsheet) that matches an existing requirement artificat ID?
2 answers
I have several hundred test cases with multiple test scripts defined in excel spreadsheets. I am planning on using the Excel Importer to load these all into RQM 2.0.1.1. However, when I to a test import of 2 test cases, each test script for each case is created.
The example:
tc1 has scripts Login and Change Password
tc2 has scripts Login and Help
2 Login scripts (exactly the same) get created.
Is there some way to tie the Login scripts together so that tc1 and tc2 point to the same script and only 1 Login script is created?
My testcase.cfg file looks like:
// this configuration file creates testscripts with testcases using self referential
// and column based data with categories
// Start looking for scripts after row 7
testscript.XLSStartRow=8
testscript.XLSWorksheetID="Testcase-Testscript"
testscript.XLSDelimeter=\n
// a new script starts when we encounter an empty row
testscript.dc:title=A
testscript.dc:description=B
// step type is defined within the spreadsheet
testscript.steps.type=C
testscript.steps.description=D
testscript.steps.title=D
testscript.steps.name=D
testscript.steps.expectedResult=E
testscript.steps.property name="comment"=F
// setup the requirement
//requirement.dc:title=B1
//requirement.dc:description=D
//requirement.alm:owner="tmcstraw"
//requirement.dc:creator="tmcstraw"
//requirement.priority=F6
//requirement.tags="$" & D4 & " " & F3 & " " & F4 & " " & F1
//requirement.XLSArtifactID=D7
// self referential links must be declared before also using column definitions
testcase.dc:title=B1
testcase.dc:description=B2
testcase.weight=D1
testcase.dc:creator=F5
testcase.alm:owner=F5
testcase.XLSArtifactID=D5
// Categories are defined in a special way
testcase.category term="Category".value=D2
testcase.category term="Function".value=D3
testcase.category term="Test Phase".value=D4
// Sections are defined differently, the first part within the quotes is the section tag, and the optional second part after the comma
// defines the name of the section. Sections that already defined within RQM will use the display name they already have
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseDesign","RQM-KEY-TC-DESIGN-TITLE")=B3
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePreCondition","RQM-KEY-TC-PRE-COND-TITLE")=B4
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCasePostCondition","RQM-KEY-TC-POST-COND-TITLE")=B5
testcase.Section("myns:com.ibm.rqm.planning.editor.section.testCaseExpectedResults","RQM-KEY-TC-ACCEPT-CRITERIA-TITLE")=B6
testcase.XLSLink=testscript
//testcase.XLSLink=requirement
Note the commented out requirements section. Is there a way to be able to turn that on so it will link a requirement (identified by the artifact ID in D7 of the excel spreadsheet) that matches an existing requirement artificat ID?
It might work if you use the line below, replacing the commented one. Try out:
testcase.requirement = requirement.identifier
Thank you for the response. That makes sense and I will try it on a couple of test cases/requirements. I guess the only problem at this point is how do I know what the identifier value is. This seems to be automatically generated as I add a new (unique) requirement/testcase/testscript. Is it possible for me to override that automatic allocation and force the identifier to be the value I want on creation?
It might work if you use the line below, replacing the commented one. Try out:
testcase.requirement = requirement.identifier
I have several hundred test cases with multiple test scripts defined in excel spreadsheets. I am planning on using the Excel Importer to load these all into RQM 2.0.1.1. However, when I to a test import of 2 test cases, each test script for each case is created.
The example:
tc1 has scripts Login and Change Password
tc2 has scripts Login and Help
2 Login scripts (exactly the same) get created.
Is there some way to tie the Login scripts together so that tc1 and tc2 point to the same script and only 1 Login script is created?
My testcase.cfg file looks like:
... deleted to save listing
testcase.XLSLink=testscript
//testcase.XLSLink=requirement
Note the commented out requirements section. Is there a way to be able to turn that on so it will link a requirement (identified by the artifact ID in D7 of the excel spreadsheet) that matches an existing requirement artificat ID?
It might work if you use the line below, replacing the commented one. Try out:
testcase.requirement = requirement.identifier