Hi
I wrote some automated tests for a qooxdoo application, in which I use this
method (from user-extensions-qooxdoo.js):
Selenium.prototype.getQxTableValue = function(locator, eventParams)
{
var qxObject = this.getQxWidgetByLocator(locator);
if (qxObject) {
if (!this.isQxInstanceOf(qxObject, "qx.ui.table.Table")) {
throw new SeleniumError("Object is not an instance of
qx.ui.table.Table: " + locator);
}
}
else {
throw new SeleniumError("No qooxdoo object found for locator: " +
locator);
}
var additionalParamsForClick = {};
if (eventParams && eventParams !== "") {
var paramPairs = eventParams.split(",");
for ( var i = 0; i < paramPairs.length; i++) {
var onePair = paramPairs[i];
var nameAndValue = onePair.split("=");
// rz: using String.trim from htmlutils.js of selenium to get rid of
// whitespace
var name = new String(nameAndValue[0]).trim();
var value = new String(nameAndValue[1]).trim();
additionalParamsForClick[name] = value;
}
}
var row = Number(additionalParamsForClick["row"]);
var col = this.__getColumnIdFromParameters(additionalParamsForClick,
qxObject);
LOG.debug("Targeting Row(" + row + ") Column(" + col + ")");
var columnModel = qxObject.getTableColumnModel();
var visibleColumns = columnModel.getVisibleColumns();
return String(qxObject.getTableModel().getValue(visibleColumns[col],
row));
};
Now instead of qx.ui.table.Table it is used a ToolTipTable. Because of this
all my tests are failing in the bold-ed area of the code above.
My command in selenium IDE looks like this:
command: assertEval
target:
selenium.getQxTableValue("qxh=app:child[0]/child[34]/child[0]/child[1]/child[1]/child[0]/child[0]/child[0]","row=1,col=0")
value: subDepartment
Thank you.
Loredana
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/getQxTableValue-on-a-ToolTipTable-tp6011347p6011347.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
