Hi,
Out of question scope, but anyway...
> I came from the world of C# and Selenium automated testing and I'm trying to find my ground with scripting in TestComplete.
While TestComplete supports XPath search, I would recommend not to use it and move to complimentary .FindXXX() methods (.FindChild, .FindAllChildren, .WaitAliasChild, .WaitPanel, ...).
Reasons:
-- They are faster than XPath search;
-- They always return TestComplete objects while XPath search can return native DOM object and this will complicate your test code;
-- They support search using regular expressions which is pretty useful and handy sometimes;
-- Their arguments are of same clarity as XPath expression.
XPath in TestComplete is a last resort means when tested application is written so poorly (from the internal design point of view) that nothing else does not work.