| || |
Capturing Automated Configuration Input Parameter
I know this is a long shot, but no harm in asking. It is a big post (with attached screenshots), but thorough and should explain our issue completely.
We are currently using Quick Test Professional 9.0 for a Functional Test Automation project. We have integrated QTP with Quality Center 8.2 (downloaded/installed the “QC – QTP Add-in”).
Our Functional Test Automation project uses a data/keyword-driven framework/methodology.
In short, we have a single QTP script (called the IJ2FTAFMainDriver) which pulls sets of data records from a database. Together, a set of data records represents a single test case. Once a set of data records has been pulled from the database, they are parsed for keyword/data, and then the appropriate Business/Control functions are called which interact with the Application Under Test.
The IJ2FTAFMainDriver script exists in QC as a Test (screenshot1).
When this Test is added to a TestSet (screenshot2), the user also populates an “Automated Configuration Input Parameter” with a unique identifier value (screenshot3). This value tells the IJ2FTAFMainDriver script which set of data records to pull from the database.
Once multiple IJ2FTAFMainDriver scripts have been added to a TestSet, it becomes difficult/impossible to determine which IJ2FTAFMainDriver script executes a particular set of data records (screenshot4).
We currently have an unused TestSet field, called “Comment” (screenshot5). We can rename the field to “Test Case ID”, and then populate it with the “Automated Configuration Input Parameter” value. This would facilitate filter/reporting. It might look something like screenshot6.
The “Automated Configuration Input Parameter” value in the QC database is located in the TESTCYCL table, as a TC_EPARAMS value. However, the value is not a simple text string. Instead, it is a CLOB, which points to an embedded XML string (screenshot7).
How can we programmatically capture the value from the XML string and automatically populate the “Test Case ID” column?
We have already contacted Mercury with this issue. They replied, not surprisingly, that it cannot be done. From past experience, I know that most things probably can be done...some are more difficult than others.
We are currently researching this issue with our DB team. However, I thought I’d post in case anyone else had ever encountered something similar.
Thanks in advance!