Best Of

It looks like you have a syntax error in your parameterization:
/:partList/part[][partType=7][{$numberOfWidgets}]/location[1]/text()

There should be a curly bracket after the dollar sign: ${variable}

Please note that when using the ${ } syntax in your DataBank xpath, the xpath may not evaluate successfully in the result window, but it will parameterize as expected during run time.

No, you cannot specify a row number when configuring a parameterized value.
Rather than creating one XPath that matches on the 6 child nodes - which results in all values getting written into the same column - I would try creating a unique XPath for each child that then will result in each value getting written into a separate column. Then you will be able to parameterize each child of your next request with a different column.

I believe you have to create a separate column in the Data Source for each value. thx

You can run Parasoft SOAtest within TeamCity by using simple integration as external command line tool.
Such integration allows to use Parasoft SOAtest’s html reports in TeamCity report-ing view.

Preparing the build steps
As TeamCity administrator add build step which will start soatestcli/soatestcli.exe.
I'm uisng command line execution (Executable with parameter) as build step

In this step following command line allows me to run SOAtest cli interface and change defaults parameters:
soatestcli.exe -data “c:\SOAtest_workspace” -config “builtin://Demo Configuration” -localsettings “c:\My_Tests\localsettings.properties” -report %system.teamcity.build.workingDir%\Reports -fail

Note: I'm using locations/configuration options which could be changed and/or parametrized:
c:\SOAtest_workspace – SOAtest working workspace
builtin://Demo Configuration - SOAtest default run configuration
c:\My_Tests\localsettings.properties - SOAtest local settings for my run
%system.teamcity.build.workingDir%\Reports – report location for SOAtest, %system.teamcity.build.workingDir% - TeamCity variable

HTML Report view
Add SOAtest’s report location in TeamCity > Build Configuration Settings > General Settings > Artifacts paths

Add additional Report Tab View for TeamCity Project > Administration > Project Settings > Report Tabs

Avoiding increasing size of artifacts from test
I'm recommending to enable option “Clean all files in the checkout directory before the build” in TeamCity. It allows to keep the most recent report after SOAtest execution in Report Tabs

Note: that additional option -fail is not mandatory, I'm using it to pass information to TeamCity system about failures during tests run, and will mark whole execution as failure if any test end with an error.

I believe the password will be masked/encoded in the property file generated by clicking the Export Configuration Settings button in the DB Tool editor.

You could set up multiple Excel worksheets, each of which has the different inputs that you want to choose from. You could then use a Data Group data source within your test scenario. The Data Group data source will allow you to easily switch between different Excel data sources, and using it you can choose the Excel data source that contains the set of data the user wants for that test run. The user can select which Excel data source to use in the Data Group data source either from the UI, or by specifying an argument during command line execution. See the SOAtest documentation for more details on Data Group data sources.

If the look-up information is already available, you may add the datasource (e.g, Excel, CSV, table) to your test suit and simply select the specific row of data you wish to compare against the service response or against a second datasource. For example:

@MichaelG I reproduced the issue on my end and found out that IBM has refactored it's driver class. When connecting the data source is looking for a legacy driver that isn't there any more. There is another way though!! (sans restart) Select "Custom" for the driver class and fill out the Driver class, URL, etc.. information. (Pictured)