Forum Discussion
Hi,
I am second to Robert. TestComplete can do everything Selenium can do (except headless test execution) with a lot of things supported natively, thus not requiring usual Selenium workarounds (e.g. accessing browser windows like Save/Open file, actions over controls that are out of viewport, etc.). So the only benefit here is the (possible) reuse of the existing Selenium code.
On the other hand, we tried to add Selenium test to our TestComplete suite once and our experience was quite negative: we got a requirement to embed all Selenium infrastructure into TestComplete test suite (JARs, Maven, etc.) which significantly complicated test suite deployment and configuration and at the same time this did not help us significantly because of essential Selenium's inability to connect to the already running browser instance.
Related Content
- 2 years agoragul
Recent Discussions
- 50 minutes agoSubhraDas
- 7 hours agoJacobjacob44